4 ms·

Bugs in spec != bugs in code. This is expressly moving the goalposts.

• gnulinux 5y ago
  Even if this were true my point (2) still stands. But it really isn't true because spec is part of the code. If your formalism is wrong, irregardless of whether implementation is correct, your code will behave wrong. There is absolutely no goal post moving. If my program is wrong, I can't tell my user "well, my unittests are all passing and I have 100% code coverage".
  • junon 5y ago
    > Even if this were true my point (2) still stands. And it is completely beside the point of the original argument. I was never arguing against your second point.