- As Simple as Possible, but No Simpler
- Bugs Are Contagious
- A Good Name Is the Best Documentation
- Generalization Takes Three Examples
- The First Lesson of Optimization Is Don’t Optimize
- Code Reviews Are Good for Three Reasons
- Eliminate Failure Cases
- Code That Isn’t Running Doesn’t Work
- Write Collapsible Code
- Localize Complexity
- Is It Twice as Good?
- Big Teams Need Strong Conventions
- Find the Pebble That Started the Avalanche
- Code Comes in Four Flavors
- Pull the Weeds
- Work Backward from Your Result, Not Forward from Your Code
- Sometimes the Bigger Problem Is Easier to Solve
- Let Your Code Tell Its Own Story
- Rework in Parallel
- Do the Math
- Sometimes You Just Need to Hammer the Nails
Last active
December 28, 2025 17:01
-
-
Save jamesmurdza/d5f60215b6fb80469994d8d20ec46ab0 to your computer and use it in GitHub Desktop.
Chris Zimmerman's The Rules of Programming
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment