Just recently, I found this REAL bug sitting on the edge of my screen while coding – the (admittedly quite nerdy) irony of it is hard to miss. Rest assured, I ‘guided’ it away from ‘the system’ to the outside as gently as possible, resisting any impulse to to squash it using the keyboard on the spot. You know the rule, “Never touch a running system”, and unfortunately double-clicking and pressing <DEL> didn’t seem to work here.
A more funny (and nerdy) take on debugging code is this video by Atlassian called “Software Bugs” that made my morning:
“All bugs welcome! … create some buzz, … and when the spider gets here, I guess we can start talking web development”
Some more in-depth understanding of the issues involved is provided in this talk by Prof. Stephen Freund on “Stopping the Software Bug Epidemic” – he also touches on the halting problem, memory leaks and parallel code execution.
Although the talk is very informative throughout while presenting the basic issues in an entertaining way, I wonder why he didn’t mention the “Dining Philosophers Problem” – I guess it’s hard to trace deadlocks by automated checkers? In addition, he only refers to the (ancient) waterfall-modell of software engineering. Some comments on how more modern development philosophies (eXtreme programming, agile etc.) fit into the picture would have been nice. Anway, Happy deBugging!