News for hackers. Stuff that matters.

A comment on A sufficiently detailed spec is code. Parent comment

Re:A sufficiently detailed spec is code by naruhodo on Thursday March 19, 2026 @02:28AM (#47435668)
The source code does what it does, including bugs.

So unless you want bugs to be your specification, you actually need to specify what you want.

[ Parent | on HN ]
Re:A sufficiently detailed spec is code by lunar_mycroft on Thursday March 19, 2026 @02:48AM (#47435790)
A corollary to the linked article is that a specification can also have bugs. Having a specification means that you can (in theory) be sure you have removed all inconsistencies between that specification and the source code, but it does not mean you can know you have removed all bugs, since both the spec and the source code could have the same bug.
[ Parent | on HN ]
Re:A sufficiently detailed spec is code by Panzerschrek on Thursday March 19, 2026 @03:36AM (#47436081)
A bug is a difference between specification and its implementation. In no specification exists, there is no bug (strictly speaking). In a more wide sense a bug is a difference between some implementation and user's expectations, but such expectations may be considered to be some sort of non-formal specification.
[ Parent | on HN ]