Intentional Code - Minimalism in a World of Dogmatic Design
summary
Argues that small, intentional choices beat dogmatic patterns: every character matters—whitespace and line breaks improve comprehension—and concrete refactors cut system cruft. Collapsed a fragmented system of 64 modules → 1 repo (19 build pipelines across 3 environments) and reduces deploy time from ~50 minutes to 3 minutes without changing logic. Chooses a tiny bespoke tool—a 200-line program instead of heavyweight frameworks—to avoid dependency bloat. Uses simple tests: fewer moving parts, operable in production, and minimal public surface area.
AI-written summary · about
chapters (24)
- 0:00The case for intentional code
- 2:05Avoiding thoughtless design
- 3:33Rethinking design patterns
- 6:30Software as literature
- 8:24Defining software's purpose
- 11:03Moving beyond rigid dogmas
- 13:05Macro and micro design
- 14:24Form, flow, and cohesion
- 16:12Managing inherent complexity
- 18:13The temporality of design
- 21:45Reducing structural bloat
- 25:07Trimming complexity
- 26:47Avoiding uniform design
- 29:10Complexity and cognitive load
- 31:39Qualities of good code
- 33:14The cost of abstraction
- 34:31Deep vs. shallow modules
- 36:21Finding the right abstractions
- 37:38Avoiding design absolutism
- 40:20Testing design quality
- 40:44Optimizing for change
- 42:00Cultivating intentionality
- 44:42Further reading and wrap-up
- 45:37Q&A session
related talks
53mIntentional Code - Minimalism in a World of Dogmatic Design
50mIntentional Code - Minimalism in a World of Dogmatic Design
50mIntentional Code - Minimalism in a World of Dogmatic Design
57mIntentional Code - Minimalism in a World of Dogmatic Design
27mThe Superpower of Intentional Architecture
01h 03mTactical Design
46mFrontend Minimalism in Action: Do More With Less JavaScript
33mGet the core right and the resilient code will follow