The Catcher in the Code
summary
Code is communication: concrete claim is that good code must use or change easily, tell a story, and be named and packaged to map the domain. Examples include access modifiers used to shape intent, a broken Visitor with a no-arg single method, an interface taking a Map→Map, over‑abstraction that lets a shopping cart sell cats or boats, and the brain‑friendly mountain pattern for legacy methods. Warns about risky reflection and the bubble tower effect. Ends with four rules: assume a hostile maintainer, name things well, think at every change, and tell stories.
AI-written summary · about
chapters (18)
- 0:00Catcher in the Code metaphor
- 1:50Code as communication
- 3:14Storytelling through code
- 5:21Code design focus
- 7:30Code as map and diary
- 9:20Code inconsistency impact
- 10:43Renaming code models
- 12:31Naming and metaphors
- 13:59Misnamed design patterns
- 15:03Coupling and cohesion
- 16:47Mountain pattern solutions
- 18:36Simple vs complex code
- 20:43Over-decoupling dangers
- 21:46Bullied code understanding
- 24:43Language switching impact
- 26:56Fixing bullied code
- 28:21Four rules for code storytelling
- 31:56Stop coding, tell stories
