The Best Practices Quick Reference provided in this appendix compiles the best practice titles across all the chapters into a concise list; for each best practice, the first, sometimes tongue-in-cheek title of each best practice appears in the left column and the second, more serious title in the right column. Once you have studied the individual best practices, you can use Table A-1 as a checklist, to be reviewed before you begin coding a new program or application.
Table A-1. Best Practices Quick Reference
Chapter 1, The Big Picture
Software is like ballet: choreograph the moves or end up with a mess.
Put into place a practical workflow that emphasizes iterative development based on a shared foundation.
Deferred satisfaction is a required emotion for best practices.
Hold off on implementing the body of your program until your header is stable and your tests are defined.
Contracts work for the real world; why not software, too?
Match strict input expectations with guaranteed output results.
Don't act like a bird: admit weakness and ignorance.
Ask for help (or at least take a break) after 30 minutes on a problem.
Five heads are better than one.
Review and walk through one another's code; then do automated code reviews.
Don't write code that a machine could write for you instead.
Generate code whenever possible.
We need more than brains to write software.
Take care of your "host body": fingers, wrists, back, etc.
Chapter 2, ...