Quotes About Debugging

Programming "was just the most bizarre situation, because you're used to doing something and thinking you've done it right," he later said. "But it isn't right. You just don't notice it isn't right. On a computer there is no consolation in discovering you're almost right. Almost means you're still just wrong." Even

Everyone knows that debugging is twice as hard as writing a program in the first place. So if you are as clever as you can be when you write it, how will you ever debug it?

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.

Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?

Don't comment bad code—rewrite it.

There has never been an unexpectedly short debugging period in the history of computers.

Great QA requires a perverse and sometimes sadistic intuition for what will cause software to blow up, crash, or endlessly hang. Maxine once heard a joke: "A QA engineer walks into a bar. Orders a beer. Orders zero beers. Orders 999,999,999 beers. Orders a lizard. Orders negative one beer. Orders a 'sfdeljknesv.

Fixing bugs is not making progress. You aren't paid to debug. Debugging is waste.

The warmth and the soft glow of the tubes also attracted moths, which would fly through ENIAC's innards and cause short circuits. Ever since, the process of fixing computer problems has been known as debugging.

This was a leap forward in computing—or it would have been, if not for the moths. Because vacuum tubes glowed like lightbulbs, they attracted insects, requiring regular "debugging" by their engineers. Also like lightbulbs, vacuum tubes often burned

There really was, as [Tom] West had often said, more to building a computer than designing and debugging a Central Processing Unit. Someone had to dream up its general outlines in the first place. Someone had to make sure the computer worked compatibly with the company's existing line of peripheral equipment. Someone had to set goals of cost and performance and see that they could be met. 278

It's not a bug — it's an undocumented feature.

Debugging — the classic mystery game where you are the victim, the detective, and the murderer.

There has never been an unexpectedly short debugging period in the history of computers.

Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code.

It is surprising how little page space is devoted to bugs and debugging in most introductory programming textbooks.

With enough eyeballs, all bugs are shallow.

The only code that doesn't have bugs is code that is not yet written.

A program that has not been tested does not work.

Program testing can be used to show the presence of bugs, but never to show their absence!

Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code.

Sometimes it pays to stay in bed in Monday, rather than spending the rest of the week debuging Monday's code.

Testing proves a programmer's failure. Debugging is the programmer's vindication.

If debugging is the process of removing software bugs, then programming must be the process of putting them in.