Bugs Quote by Edsger Dijkstra

If debugging is the process of removing bugs, then programming must be the one to put them in

— Arshad Feeroz

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

— Anonymous

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

“Debugging: what an odd word. As if "bugging" were the job of putting in bugs, and debugging the task of removing them. But no.…

— Ellen Ullman

Given enough eyeballs, all bugs are shallow (e.g., given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and…

— Eric S. Raymond

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

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

— Richard E. Pattis

My software never has bugs. It just develops random features.

— Anonymous

“Pragmatic Programmers are different. We are driven to find our bugs now, so we don't have to endure the shame of others finding our…

— Andrew Hunt

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you…

— Brian Kernighan

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

— Edsger Dijkstra