3 ms·
If the formal specification is wrong, the component is still broken in practice. Your distinction is convenient as a vehicle for feeling better about your code
by krageon 6y ago
If the formal specification is wrong, the component is still broken in practice. Your distinction is convenient as a vehicle for feeling better about your code (and I would argue you should feel good about writing such code), but it doesn't really have any bearing on the problem given the way you present it here.
- lmm 6y ago> If the formal specification is wrong, the component is still broken in practice. What does it even mean for an internal specification to be "wrong"? The specification for the system can be wrong, and maybe the component wouldn't be useful in a correctly-specified system, but even then I think it's misleading to say the component is "broken".