Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.
| 0. | Don’t sweat the small stuff. (Or: Know what not to standardize.) Say only what needs saying: Don’t enforce personal tastes or obsolete practices. |
| 1. | Compile cleanly at high warning levels. Take warnings to heart: Use your compiler’s highest warning level. Require clean (warning-free) builds. Understand all warnings. Eliminate warnings by changing your code, not by reducing the warning level. |
| 2. | Use an automated build system. Push the (singular) button: Use a fully automatic (“one-action”) build system that builds the whole project without user intervention. |
| 3. | Use a version control system. The palest of ink is better than the best memory (Chinese proverb): Use a version control system (VCS). Never keep files checked out for long periods. Check in frequently after your updated unit tests pass. Ensure that checked-in code does not break the build. |
| 4. | Invest in code reviews. Re-view code: More eyes will help make more quality. Show your code, and read others’. You’ll all learn and benefit. |