| ▲ | naruhodo 5 hours ago | |
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. | ||
| ▲ | lunar_mycroft 4 hours ago | parent | next [-] | |
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. | ||
| ▲ | Panzerschrek 3 hours ago | parent | prev [-] | |
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. | ||