Post

I don’t agree with you Sylvain and I think the article does not either. People that have written specs that need to be implemented by several other systems, that spend countless hours to refine it, know that uncertainty and unclarity creeps in at every opportunity.

So to describe the what something like code ends up being better. And between English code and Java code, I know what I prefer to read, understand and navigate. Java is less expressive and more deterministic and syntactically structured. These constraints make it a good descriptor of WHAT.

But there is something to the cascading for artéfacts. A WHY artefact not to lose the big picture (say a readme), the HOW (agents.md, architecture.md) as a constraining set of requests (I say requests because the coding agent can ignore them), the high level WHAT (spec.md) and the real WHAT (code).

What is fascinating is that coding agents can adjust one based on the other and iterate on them like a pyramid. And coding agents do “fill the blank”, the unknown, the unsaid.