Code Quote by Brian Kernighan

“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…

— Brian Kernighan

When debugging, novices insert corrective code; experts remove defective code.

— Richard E. Pattis

The most effective debugging tool is still careful thought, coupled with judiciously placed print statements.

— Brian Kernighan

If you want more effective programmers, you will discover that they should not waste their time debugging, they should not introduce the bugs to…

— Edsger Dijkstra

An interactive debugger is an outstanding example of what is not needed - it encourages trial-and-error hacking rather than systematic design, and also hides…

— Harlan Mills

Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.

— Eric S. Raymond

Another effective [debugging] technique is to explain your code to someone else. This will often cause you to explain the bug to yourself. Sometimes…

— Brian Kernighan

“In debugging, errors are seen not as false but as fixable. This is a state of mind that makes it easy to learn from…

— Sherry Turkle

The hardest part of the software task is arriving at a complete and consistent specification, and much of the essence of building a program…

— Fred Brooks

Programming is the art of algorithm design and the craft of debugging errant code.

— Ellen Ullman

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

— Anonymous

The process of debugging, going an correcting the program and then looking at the behavior, and then correcting it again, and finally iteratively getting…

— Nicholas Negroponte