- "Don’t just echo the code with comments – make every comment count."
"Make sure comments and code agree."
- "Don’t comment bad code – rewrite it."
— "The Elements of Programming Style" by Kernighan and Plauger, 1974
- "It’s important to communicate what the code should be doing.” – Joe Kunk
- “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
- “If debugging is the process of removing software bugs, then programming must be the process of putting them in. ” – Edsger Dijkstra
- “Walking on water and developing software from a specification are easy if both are frozen.” – Edward V. Berard
- “First, solve the problem. Then, write the code.” – John Johnson
- “Should array indices start at 0 or 1? My compromise of 0.5 was rejected without, I thought, proper consideration.” – Stan Kelly-Bootle
- “Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.” – unknown (attributed to John F. Woods, Rick Osborne, Martin Golding)
- “Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” – Martin Fowler
- “Programs must be written for people to read, and only incidentally for machines to execute.” – Abelson/Sussman
- “Computers are good at following instructions, but not at reading your mind. ” – Donald Knuth
- “Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.” – Rick Cook, The Wizardry Compiled
- „Do unto the next developer as you would have them do unto you“ – Joe Kunk