News for hackers. Stuff that matters.
Re:AlphaProof Code by jwpapi on Tuesday November 10, 2026 @05:44PM (#50447362)
I have recenctly tried to move my codebase more to spec driven development, but I aborted it. For my use case it felt wrong. It just creates drift and more prose explaining what I need.

I’m not saying I’m right, but I want to understand. What’s the benefits of raw specs with AI, when AI can read the source of truth and explain to you?

Re:AlphaProof Code by fooker on Tuesday November 10, 2026 @09:31PM (#50449117)
The thesis is that you can come up with a tight spec that defines what correctness means for you. Then the AI writes lean proofs that your code follows this spec.

In practice, for real systems, this much moves source of truth, as you have pointed out.

However, there is a clear 'compactness' advantage for specs.

Specs can either define the operational (what it does) or the denotational semantics (what it is) for a system, while the code can only be operational. Some things are just easier and better defined in denotational semantics.