Intentional Code - Minimalism in a World of Dogmatic Design
summary
Argues that every single character matters and that dogmatic rules like Clean Code often harm intent; demonstrates collapsing an overengineered system—refactoring 64 modules into three and removing 19 build pipelines to yield a single logical program with about 30 APIs maintained by a team of three. Uses class diagrams, diffs and local refactoring (co-location and directories instead of extra packages) to show measurable reduction in surface area, cognitive load and deploy complexity, and offers concrete tests: fewer moving parts, operable in production, and easy to change.
AI-written summary · about
chapters (9)
- 0:00Start
- 9:44SOFTWARE REALLY IS
- 12:19COMMUNICATING INTENT
- 15:34THE CENTRAL CHALLENGE OF SOFTWARE DESIGN
- 22:07STRUCTURAL DESIGN IS OFTEN TOO BIG
- 31:48WHAT DOES COMPLEXITY ACTUALLY MEAN?
- 35:05INTENTIONALITY IS CARING ABOUT THE COST OF ABSTRACTION
- 37:11DEEP VS SHALLOW MODULES
- 40:06AN END TO ABSOLUTISM
related talks
58mIntentional 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
39mYou should stop writing code
40mGood Code: What, Why, and How to Get There
57mCore Software Design Principles for Programmers
01h 03mTactical Design
25mIs clean code dead?