A sufficiently detailed spec is code
dokdev
11 points
2 comments
March 18, 2026
Related Discussions
Found 5 related stories in 76.4ms across 8,303 title embeddings via pgvector HNSW
- A sufficiently detailed spec is code signa11 · 128 pts · March 19, 2026 · 100% similar
- Type Out the Code theanonymousone · 13 pts · May 19, 2026 · 55% similar
- Show HN: Spec-Driven Development Workflow for Claude Code sermakarevich · 11 pts · May 22, 2026 · 53% similar
- A Couple Million Lines of Haskell: Production Engineering at Mercury unignorant · 127 pts · May 03, 2026 · 50% similar
- Spectre Programming Language asdkop · 29 pts · May 15, 2026 · 50% similar
Discussion Highlights (2 comments)
internet_points
Well done for actually trying and failing to reproduce their results. But the point from the original comic version kind of makes it seem like specs are useless, which I don't believe is true. Just like reimplementations can be useful (directly so for property testing or golden testing, but also for learning what things worked and what didn't), a specification can be useful even though it is informal or incomplete in that it guides the real implementation. (Like "plan mode", for you vibers.)
GeoSys
It's so easy to make a specification which can't be implemented (or shouldn't be). Very often, I go back and tweak the specification, after I start the implementation and figure out which assumptions are wrong ...