Here is a list of 10 programming quotes I picked from this longer list, and what I learned from each:
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.
Lesson: Always assume that your code is buggy and code accordingly.
Be careful about using the following code — I’ve only proven that it works, I haven’t tested it.
Lesson: Always test your code.
Good code is its own best documentation. As you’re about to add a comment, ask yourself, “How can I improve the code so that this comment isn’t needed?”.
Lesson: Write clear maintainable code.
Incorrect documentation is often worse than no documentation.
Lesson: Make sure your documentation really reflects what your code is doing and vice verse.
Measuring programming progress by lines of code is like measuring aircraft building progress by weight.
Lesson: The number of lines of code is irrelevant in measuring software development progress, measure by what the code does and how fast it does it.
Just because the standard provides a cliff in front of you, you are not necessarily required to jump off it.
Lesson: Do not blindly follow any standard, understand first.
The most important single aspect of software development is to be clear about what you are trying to build.
Lesson: Understand the problem first, then build the solution.
Good programmers use their brains, but good guidelines save us having to think out every case.
Lesson: Understand and use software design patterns whenever possible.
Simplicity is the ultimate sophistication.
Lesson: No comment.
The primary duty of an exception handler is to get the error out of the lap of the programmer and into the surprised face of the user. Provided you keep this cardinal rule in mind, you can’t go far wrong.
Lesson: Apply exception handling liberally across all your programs.