21 rules from 《The Rules of Programming》

Rule 1: As Simple as Possible, but No Simpler

Rule 2: Bugs Are Contagious

Rule 3: A Good Name Is the Best Documentation

Rule 4: Generalization Takes Three Examples

Rule 5: The First Lesson of Optimization Is Don’t Optimize

Interlude: In Which the Previous Chapter Is Criticized

Rule 6: Code Reviews Are Good for Three Reasons

Rule 7: Eliminate Failure Cases

Rule 8: Code That Isn’t Running Doesn’t Work

Rule 9: Write Collapsible Code

Rule 10: Localize Complexity

Rule 11: Is It Twice as Good?

Rule 12: Big Teams Need Strong Conventions

Rule 13: Find the Pebble That Started the avalanche

Rule 14: Code Comes in Four Flavors、

Rule 15: Pull the Weeds

Rule 16: Work Backward from Your Result, Not Forward from Your code

Rule 17: Sometimes the Bigger Problem Is Easier to Solve

Rule 18: Let Your Code Tell Its Own Story

Rule 19: Rework in Parallel

Rule 20: Do the Math

Rule 21: Sometimes You Just Need to Hammer the Nails