Fractal Architecture
summary
Argues that cutting time spent reading code beats shaving write time, with concrete measures: use cyclomatic complexity and object activation count (example method shows cyclomatic 3 and six activated objects), aim for at most seven interacting things — the magic number seven — at any abstraction level. Advocates encapsulation and referential transparency (pure functions) so complexity doesn’t leak up, shows C# examples (SQLConnection/SqlCommand, a create method) and a fractal “hex flower” model of nested, self-similar modules.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:50Reading vs Writing
- 5:31Readability
- 12:16The Magical Number
- 13:17Chunks
- 14:04Longterm memory
- 18:58Shortterm memory
- 20:46Reading the code
- 21:54Counting objects
- 22:30SQL connection
- 22:59State changes
- 24:38Hex flower
- 25:18Create method
- 27:27Entry point
- 30:29Object Activation
- 31:44Details Matter
- 35:00Encapsulation
- 35:58A shortcut to encapsulation
- 37:40No side effects
- 38:53Same output
- 39:55Pure function
- 42:54Summary
- 44:39Fractal Hex Flower
- 45:44Q A
related talks
01h 02mFractal Architecture
54mFractal Architecture
46mMeet The Social Side of Your Architecture
44mFractal Geometry of Software Design
01h 29mArchitecture Beyond Clean & Hexagonal
45mConquering complexity: refactoring JavaScript projects
50mIntentional Code - Minimalism in a World of Dogmatic Design
58mIntentional Code - Minimalism in a World of Dogmatic Design