Skip to content

Debugging

Deleted code is debugged code. (Jeff Sickel)
They don’t make bugs like Bunny anymore. (Olav Mjelde)
Would you rather Test-First, or Debug-Later? (Robert Martin)
One of my most productive days was throwing away 1000 lines of code. (Ken Thompson)
If debugging is the process of removing bugs, then programming must be the process of putting them in. (Edsger W. Dijkstra)
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. (Brian W. Kernighan)
Each new user of a new system uncovers a new class of bugs. (Brian W. Kernighan)
It’s hard enough to find an error in your code when you’re looking for it; it’s even harder when you’ve assumed your code is error-free. (Steve McConnell)
Program testing can be a very effective way to show the presence of bugs, but is hopelessly inadequate for showing their absence. (Edsger W. Dijkstra)
The trick is to fix the problem you have, rather than the problem you want. (Bram Cohen)
Another effective debugging technique is to explain your code to someone else. This will often cause you to explain the bug to yourself. Sometimes it takes no more than a few sentences, followed by an embarrassed ‘Nevermind. I see what’s wrong. Sorry to bother you.’ This works remarkbly well; you can even use non-programmers as listeners. One university computer center kept a teddy bear near the help desk. Students with mysterious bugs were required to explain them to the bear before they could speak to a human counselor. (Brian W Kernighan)
Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday’s code. (Dan Salomon)
Any sufficiently advanced bug is indistinguishable from a feature. (Rich Kulawiec)
When debugging, novices insert corrective code; experts remove defective code. (Richard Pattis)
The only way for errors to occur in a program is by being put there by the author. No other mechanisms are known. Programs can’t acquire bugs by sitting around with other buggy programs. (Harlan Mills)
There are two ways to write error-free programs; only the third one works. (Alan J. Perlis)
When you catch bugs early, you also get fewer compound bugs. Compound bugs are two separate bugs that interact: you trip going downstairs, and when you reach for the handrail it comes off in your hand. (Paul Graham)
As soon as we started programming, we found to our surprise that it wasn’t as easy to get programs right as we had thought. Debugging had to be discovered. I can remember the exact instant when I realized that a large part of my life from then on was going to be spent in finding mistakes in my own programs. (Maurice Wilkes)
Bug, n: An elusive creature living in a program that makes it incorrect. The activity of “debugging”, or removing bugs from a program, ends when people get tired of doing it, not when the bugs are removed. (Datamation)
If you torture the data enough, it will confess. (Ronald Coase)

2 Comments

Leave a Comment

Trackbacks

  1. ccleaner
  2. forum

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: