Post

Increasingly convinced that specs are now the source and that code is an artifact akin to a lockfile.

Spec-driven development is extremely useful, and that's what planning is done properly. Although, at least for now, plans have to be relatively small and digestible. The problem with specs-as-source is that if the spec was sufficiently complete it would (almost) be the source code itself.

Philip Nuzhnyi

@callmephilip.com

Specs are great but insufficient, I find. They need to be accompanied by additional lower level architectural requirements and considerations: requirements around information hiding, acceptable code complexity, module boundaries etc. A lot of these are enforceable via static analysis tooling

18/9/26, 10:52 am0 reposts0 likes

No replies yet.