Metaphors We Compute By
summary
Metaphors shape engineering decisions and change which solutions get built concrete examples show this: a framing experiment primes 75% chose punishment when crime is a beast while a virus frame produces remedial policies mathematical tools back up designs — queuing theory for load, graph theory for routing and epidemic math to prove why rumour-mongering maps to epidemics enabled reliable replication metaphors explain why containers as shipping containers and microservices (an Erlang‑like model) catch on and how the resulting systems actually behave
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:47Argument is War
- 2:58Argument is Dance
- 4:33Feminism
- 6:20People
- 7:03Warning
- 7:28Wrestling with inclusion
- 8:03Computers
- 8:59Metaphors Enable Understanding
- 9:49Metaphors Are OnetoOne Mapping
- 10:26Geometry of Meaning Semantics
- 11:11Metaphors Preserve Cognitive Topology
- 12:14The Problem with Metaphors
- 13:21Adapting to Our Tools
- 14:39Metaphors and Code
- 17:46Types
- 18:56Set
- 19:44Stack
- 19:58Data Structures
- 20:43Graph Theory
- 22:24Epidemics
- 23:22Distributed System Literature
- 24:22Containers
- 25:22microservices
- 26:42conclusion
related talks
01h 02mThinking Like an Architect
05mLike Software, Buildings Are Made Of People
49mMetaphorisms Deriving Divide and Conquer Recursive Programs
05mIgnite: Magic of Application Modeling
48mTechnical Modeling as a Practice
01h 00mDesign Idioms from an Alternate Universe
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas
41mHow Programs Learn, and What Happens After They're Built