"... [B]egin with cleaning up our language by no longer calling a bug a bug but by calling it an error. It is much more honest because it squarely puts the blame where it belongs, viz. with the programmer who made the error. The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation."
EWD 1036: On the cruelty of really teaching computing science [0]
> [That it is normal to have bugs] is not an indictment of software engineers but the result of the inherent complexity of software; a complex software system deals with not millions or billions, but trillions of different types of events.
To which Dijkstra has this to say about the source of the complexity:
"Many software projects carried out in the past have been overly complex and, consequently, full of bugs and patches. Mainly the following two circumstances have been responsible for this:
1. dramatical increase of processor speeds and memory sizes, which made it seem as if the sky were the limit; only after the creation of a number of disastrously complicated systems it dawned upon us, that our limited thinking ability was the bottleneck;
2. a world that in its desire to apply those wonderful new machines became over-ambitious; many programmers have yielded to the pressure to stretch their available programming technology beyond its limits; this was not a very scientific behaviour, but perhaps stepping beyond the limit was necessary for discovering that limit's position."
EWD 648: "Why is software so expensive?" An explanation to the hardware designer. [1]
I hazard a third: a receiving population geewhized and subsequently hoodwinked into accepting low standards as an inevitable trade-off for all the societal benevolence that software has wrought.
I disagree with EWD, I find the distinction between a "bug" and an "error" helpful. In any robustly engineered system, existence of a bug means that multiple errors have been made by multiple people. Singling out "the programmer who made the error" is not only unhelpful, it's misleading and disingenuous to even try.
If I write an Outlook networking server that handles 100k req/s, and it fails in production when someone points 200k req/s at it, there is a bug. Whose error is it? Is it my fault for writing a component that only handles 100k req/s? Is it the code-reviewer who didn't catch that it only handles 100k req/s? Is it the team lead who told the programmer it needed to handle 100k req/s? Is it the project manager who assigned this task to a junior engineer who can't be trusted to know that the system might need to handle more than 100k req/s? Is it the business leaders who laid off everyone who knew it would need to handle way more than 100k req/s? Is it the engineers who wrote load tests that didn't reach 200k req/s? Is it the operations team that configured this in a way where it can get 200k req/s?
In reality any one of these people could have made a decision that avoided this bug. There are always many errors on the critical path of a bug, identifying "the root cause" means you have already made a leap in logic and concluded which issue(s) you are planning on addressing and which you have decided are not worth tackling.
> In any robustly engineered system, existence of a bug means that multiple errors have been made by multiple people.
You don't find it at all odd to claim a "robustly engineered system" but then also find "multiple errors" in it? Or perhaps by "robustly" you mean a great deal of resources was thrown at it?
Forgive me, for I fall short of Dijkstra's advice here: "A programmer that talks sloppily is just a disaster. Excellent mastery of his native tongue is my first selection criterion for a prospective programmer; good taste in mathematics is the second important criterion." [0]
Back to reading the dictionary for me.
> If I write an Outlook networking server that handles 100k req/s, and it fails in production when someone points 200k req/s at it, there is a bug.
You're right: If there's no standard of correctness, then there are no errors. Ex falso quodlibet.
"... [B]egin with cleaning up our language by no longer calling a bug a bug but by calling it an error. It is much more honest because it squarely puts the blame where it belongs, viz. with the programmer who made the error. The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation."
EWD 1036: On the cruelty of really teaching computing science [0]
> [That it is normal to have bugs] is not an indictment of software engineers but the result of the inherent complexity of software; a complex software system deals with not millions or billions, but trillions of different types of events.
To which Dijkstra has this to say about the source of the complexity:
"Many software projects carried out in the past have been overly complex and, consequently, full of bugs and patches. Mainly the following two circumstances have been responsible for this:
1. dramatical increase of processor speeds and memory sizes, which made it seem as if the sky were the limit; only after the creation of a number of disastrously complicated systems it dawned upon us, that our limited thinking ability was the bottleneck;
2. a world that in its desire to apply those wonderful new machines became over-ambitious; many programmers have yielded to the pressure to stretch their available programming technology beyond its limits; this was not a very scientific behaviour, but perhaps stepping beyond the limit was necessary for discovering that limit's position."
EWD 648: "Why is software so expensive?" An explanation to the hardware designer. [1]
I hazard a third: a receiving population geewhized and subsequently hoodwinked into accepting low standards as an inevitable trade-off for all the societal benevolence that software has wrought.
[0] https://www.cs.utexas.edu/~EWD/transcriptions/EWD10xx/EWD103...
[1] https://www.cs.utexas.edu/~EWD/transcriptions/EWD06xx/EWD648...