Quotes & Sayings About Programming Bugs

Software development is the process of creating a computer software.
It includes preparing a design, coding the program, and fixing the
bugs. The final goal of software development is to translate user
needs to software product, while continuously improving the team
and the process. — Paulo Caroli

Who can afford to do professional work for nothing? What hobbyist can put three man-years into programming, finding all bugs, documenting his product, and distributing it for free? — Bill Gates

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

Debugging: what an odd word. As if "bugging" were the job of putting in bugs, and debugging the task of removing them. But no. The job of putting in bugs is called programming. A programmer writes some code and inevitably makes the mistakes that result in the malfunctions called bugs. Then, for some period of time, normally longer than the time it takes to design and write the code in the first place, the programmer tries to remove the mistakes. — Ellen Ullman

Greenspun's Tenth Rule of Programming: any sufficiently complicated C or Fortran program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp. — Philip Greenspun

One of the primary reasons that abstraction is overloved is that a completed program full of the right abstractions is perfectly beautiful. But there are very few completed programs, because programs are written, maintained, bugs are fixed, features are added, performance is tuned, and a whole variety of changes are made both by the original and new programming team members. Thus, the way a program looks in the end is not important because there is rarely an end, and if there is one it isn't planned. — Richard P. Gabriel

I like my code to be elegant and efficient. The logic should be straightforward to make it hard
for bugs to hide, the dependencies minimal to ease maintenance, error handling complete according to an articulated strategy, and performance
close to optimal so as not to tempt
people to make the code messy with unprincipled optimizations. Clean code does one thing well.

-Bjarne Stroustrup, inventor of C++
and author of The C++ Programming
Language — Robert C. Martin

I find that writing unit tests actually increases my programming speed — Martin Fowler