Top 10 list

Automate everything

Write the test code first (before you write the class), and keep it with the class. Automate the running of your tests through a makefile or similar tool. This way, ongoing changes can be automatically verified by running the test code, and you'll immediately discover errors. Because you know that you have the safety net of your test framework, you will be bolder about making sweeping changes when you discover the need. Remember that the greatest improvements in languages come from the built-in testing provided by type checking, exception handling, etc., but those features take you only so far. You must go the rest of the way in creating a robust system by filling in the tests that verify features that are specific to your class or program.

Previous: #6 - Use bare bones methodology

Next: #8 - Write test code early

Elegance always pays off	Use bare bones methodology
First make it work, then make it fast	Automate everything
Remember the "divide and conquer" principle	Write test code early
Separate the class creator from the class user (client programmer)	Get abstract
Name classes intelligently	An indirection should have a meaning