Vibe coding vs. spec-driven development: same result, better code
The same application built three times with Claude Code, once in conversation and twice from a specification. For this application of medium complexity, vibe coding was no worse in outcome. But the code of the spec version is split along domain boundaries, and that matters for maintenance and further development.
- 20 vs. 19 of 24 acceptance scenarios passed at the first acceptance (Vibe vs. Spec)
- 16 open questions the agent raised while writing the specification
- 4,300 instead of 6,300 lines of code in the module (Spec vs. Vibe)
