Fractal Architecture
summary
Claims that reading dominates development time and that reducing cognitive load yields bigger productivity gains than faster typing; measures code by cyclomatic complexity and counted variables, aiming for an aggressive threshold of about seven items per view. Uses C# examples (a Create method that builds SQL commands and connections) to show making helpers referential transparency and strong encapsulation — pure, deterministic functions — keeps complexity local so code “fits in your head” at every abstraction level.
AI-written summary · about
chapters (18)
- 0:00Software productivity challenges
- 1:31Reading code dominates time
- 4:01Cognitive processes in code reading
- 8:59Cyclomatic complexity vs readability
- 10:43Short-term memory limits
- 13:51Long-term memory and legacy code
- 17:25Layers of abstraction
- 23:45Quantifying code readability
- 25:50Code structuring for memory
- 31:52Encapsulation and complexity
- 37:49Pure functions and transparency
- 42:01Fractal architecture and simplicity
- 46:32Learning strategies and improvement
- 52:22Refactoring complex code
- 55:31Psychology of code complexity
- 58:20Metaphors in comprehension
- 1:00:02Clean code vs SQL performance
- 1:02:18Closing remarks and Q&A
related talks
01h 00mFractal Architecture
54mFractal Architecture
45mConquering complexity: refactoring JavaScript projects
39mRead my code, or why writing readable code matters
53mIntentional Code - Minimalism in a World of Dogmatic Design
54mReadable Code: The Secret to Clean, Productive Software
46mMeet The Social Side of Your Architecture
56mKicking the Complexity Habit