A sufficiently detailed spec is code
dokdev
11 points
2 comments
March 18, 2026
Related Discussions
Found 5 related stories in 51.2ms across 3,471 title embeddings via pgvector HNSW
- A sufficiently detailed spec is code signa11 · 128 pts · March 19, 2026 · 100% similar
- Show HN: Goal.md, a goal-specification file for autonomous coding agents jmilinovich · 15 pts · March 15, 2026 · 47% similar
- Speculative Speculative Decoding (SSD) E-Reverance · 28 pts · March 04, 2026 · 45% similar
- Methods in Languages for Systems Programming (2023) surprisetalk · 17 pts · March 16, 2026 · 45% similar
- Get Shit Done: A meta-prompting, context engineering and spec-driven dev system stefankuehnel · 267 pts · March 17, 2026 · 44% 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 ...