Intentional Code - Minimalism in a World of Dogmatic Design
summary
Argues that design must be intentional: every character matters, not ritualized patterns, and shows concrete fixes — collapse an architecture of 64 independent moving parts and 19 build pipelines into a single deployable app, collocate tiny modules, remove passthrough abstractions, and refactor a messy function down to four clear lines. Recommends choosing fewer moving parts, testing operability, and preferring narrow, deep module interfaces over dogmatic frameworks — even telling developers to burn Clean Code.
AI-written summary · about
chapters (8)
- 0:00Intentional code design
- 2:15Thoughtless architectural patterns
- 11:44Software as literature
- 17:40Complexity vs intentional design
- 27:06Overdesign and cognitive load
- 32:21Intentionality vs complexity
- 41:08Design tradeoffs and compromise
- 46:24Conclusion
related talks
58mIntentional Code - Minimalism in a World of Dogmatic Design
27mThe Superpower of Intentional Architecture
33mSet Design: Putting the "Art" in "Architecture"
34mHot Garbage Clean Code is Dead
50mEmergent Design
41mUsing Boundary-Driven Development to beat code complexity
51mA Contrarian View of Software Architecture
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide