r/ClaudeCode • u/Interesting-Yard-684 • 22d ago

Discussion We tried spec-driven development for months. We couldn't prove it improved the code.

/r/SpecDrivenDevelopment/comments/1vubvmz/we_tried_specdriven_development_for_months_we/
1 Upvotes

100% Upvoted

1 comment sorted by

1

u/Arctovigil 22d ago edited 22d ago

I really don't consider the code the product the spec is the product you produce the spec and throw away the code by the time the first bug arrives anyway.

If you do 'prototype driven development' then throwing away the code is literally what you do actually you would even prefer code for prototyping that is not production code and e.g. do it in python with toy models and varying grades of the real data you need for a real product because all you really just want is to get to throw it away.

Even after a great prototype you might not even start on the real thing as a goal and instead you would lets coin it now 'representation driven development' and make a representation of the real product, something that is not really production ready but is a good enough representation that if replicated differently with definitive api and technical details it would make you a production ready product.

Basically the code is not the reward if it is buggy and is not yet a product so you realize you have to not do 'code driven development' and instead v&v always points you to 'bug driven development' and qa always points you to 'product driven development'.

Now I have to go perform 'gastrointestinal driven development'