Metaphors We Code By
summary
Argues metaphors shape code and team choices with concrete examples: OS UI terms like windows/folders/recycle bin traced to 1980s design; naming mismatches in stacks (use push/pop/top not get top or peek) and common variable name study (Peter Hilton finds “data” everywhere on GitHub). Traces technical debt back to Ward Cunningham (1992) and Martin (early 2000s), warns against quantifying it as money, reframes unpaid debt as neglect. Gives energy figures—brain ~12 W, lifetime ~10 MWh, GPT-3 ~1 GWh—and coins the extended metaphor pataphor.
AI-written summary · about
chapters (6)
- 0:00The role of metaphor in code
- 22:16Language and naming
- 28:41The dangers of over-metaphor
- 31:42Evaluating metaphors
- 35:18Technical debt as a metaphor
- 45:25Beyond metaphor
related talks
44mMetaphors We Compute By
19mThe Power of Metaphors
34mHow do our ideas about coding affect the software we create?
30mCognitive Shortcuts: Models, Visualizations, Metaphors, and Other Lies
52mFinding the Beauty in the Digital Brick
44mThe programmer's imagination
41mHow We Tell Stories In Code
49mBeautiful code: typography and visual programming
