Fractal Architecture
summary
Claim: cutting reading time boosts productivity far more than shaving edit time, achieved by designing code to fit in short‑term memory using encapsulation, aggressive thresholds and referential transparency. Concrete checks: count cyclomatic paths and active objects, aim for about seven plus or minus two chunks. Examples in C# include a repository Create method and an allocate algorithm written as a pure function so its result collapses to a single value; outcome is less cognitive load and faster onboarding (author reports months → weeks).
AI-written summary · about
chapters (14)
- 0:00Fractal Architecture intro
- 1:10Productivity in software dev
- 4:18Making code readability objective
- 10:29Cognitive limits and complexity
- 17:10Short-term memory and structure
- 25:11Cognitive constraints at all levels
- 30:39Pure functions and referential transparency
- 37:16Fractal architecture explained
- 41:07Q&A
- 42:09Signaling pure functions in languages
- 45:02Dependencies and separation
- 47:07Single responsibility and classes
- 50:24Why Haskell isn't popular
- 53:12Closing remarks
related talks
01h 02mFractal Architecture
01h 00mFractal Architecture
44mFractal Geometry of Software Design
58mIntentional Code - Minimalism in a World of Dogmatic Design
21mCognitive Psychology and the Zen of Code
46mMeet The Social Side of Your Architecture
01h 26mChaos Development: Removing Software as the Inhibitor of Agile
34mShortening the Architectural Feedback Loop