The Moderate Programmer
summary
Advice lands on concrete rules: name things three words or less and use plurals or prefixes like is/has for booleans; functions do one conceptual thing, avoid flags and more than three arguments; write tests immediately, prefer Ember integration tests and keep unit tests sparse; follow the rule of three — refactor on the third duplication and allow ugly code while exploring abstractions; give up temporarily: ask for help, take a 15‑minute break, stash or throw out drafts when they don’t work.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:15Avoiding Extremes of Behavior
- 4:46Plurals
- 7:17Components Are Functions
- 12:31Costs of the Refactor
- 13:06Give Up and Ask Someone for Help
related talks
20mGood Code is a Balancing Act
57mCore Software Design Principles for Programmers
39mClean, Concise, Collaborative Code
53mIntentional Code - Minimalism in a World of Dogmatic Design
01h 47mClean code
40mGood Code: What, Why, and How to Get There
39mRead my code, or why writing readable code matters
45m'Writing code that lasts'...or writing code you won't hate tomorrow