@b0rk Here's Jeff Atwood's version of this, also inferior to your way of expressing it: "The First Rule of Programming: It's Always Your Fault".
https://blog.codinghorror.com/the-first-rule-of-programming-its-always-your-fault/
Top-level
@b0rk Here's Jeff Atwood's version of this, also inferior to your way of expressing it: "The First Rule of Programming: It's Always Your Fault". https://blog.codinghorror.com/the-first-rule-of-programming-its-always-your-fault/ 3 comments
@swiftone @b0rk I call that "the Finger of Blame". My kid was taking a programming class last year and I explained: "The goal here is to point the Finger of Blame: What part of the code is really responsible for the problem? First you accuse the code that actually prints the wrong result. Then that code says “Nuh uh, it was like that when I got it, go blame that other guy that gave it to me.” Eventually you find the smoking gun." Julia would probably have a less recriminatory way of putting it. |
@mjd yeah in general I find that debugging advice is often very… condescending? and it makes me mad