Worth a Million Arguments
summary
Argues that arguments lose to evidence and shows concrete examples: a 2,000-train purchase discovers 1,300 stations are too small; the Vasa warship and Tacoma Narrows bridge fail from untested design; a team coils 200 km of cable in an office to validate network SLA; one developer’s optimistic-locking deployment revealed a vendor bug; a car OTA fixed cruise behavior. Recommends prototype before you port and build one train first — run lightweight experiments to reveal feasibility, performance, and risks before full commitment.
AI-written summary · about
chapters (18)
- 0:00The cost of arguments
- 1:50Measure, don't argue
- 3:53Thinking through consequences
- 5:55Example: the pencil
- 8:14Usability disconnects
- 12:37Lack of communication
- 14:01The Vasa disaster
- 17:11Feasibility and scale
- 19:14Tacoma bridge collapse
- 22:14Railway platform issues
- 24:34Hope-driven development
- 27:20Questioning requirements
- 29:17Picasso's prototypes
- 32:37Mount Rushmore design
- 36:42Managing high risks
- 39:34The ultimate prototype
- 45:36Real-world failures
- 53:15The power of prototyping
related talks
55mMisunderstanding
50mFallacies of Software Development
10mAre we arguing or are we architecting?
39mSomone is Wrong
46mTough Talk: How to Confront Your Opinion With Your Teammates?
38mFallacies of Software Development
41mWhy Software Engineers Disagree About Everything
27mMove Thoughtfully and build things