Software Is Details
summary
Argument that small, repeated choices become the system's physics: execution architecture (threading, event vs time‑triggered) and naming or API choices shape cost and changeability. Concrete examples include Google Maps zoom hiding driving direction, the left-pad incident breaking many sites, Schiaparelli's IMU assumption causing a crash, and the Java cloneable misspelling that propagated. Demonstrations include sorting algorithm experiments (permutation, bogo, sleep sort) and a tiny JS test harness that reveals real npm packages fail. Claim: measure by implementation and runtime observation; configuration is code.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:24Quote Meir M Lehman
- 3:48Quote Edsger W Dijkstra
- 5:40Quote Peter Weinberger
- 5:51Quote Marissa Mayer
- 6:51Quote Will Gompertz
- 8:18Software Architecture
- 10:42Quote Grady Booch
- 14:29Example: Google Maps Paris
- 16:40Execution software architecture
- 17:58Cloneable
- 22:21Quote Tom Gilb
- 25:00WordFriday
- 27:10Quote Jack W Reeves
- 27:33Quote Donald Knuth
- 28:15Sort
- 34:06Left-pad incident
- 37:17Quote David Parnas
- 38:05The world of code
- 40:06Schiaparelli anomaly
- 42:26Assumptions
- 45:35Quote Neal Ford
- 48:24Quote Robert M Pirsig
related talks
01h 00mEngineering Software
43mGo Ahead, Make a Mess
35mCraft, Engineering, and the Essence of Programming
01h 07mSmall Is Beautiful
41mHow We Tell Stories In Code
21mModifiable Software Systems: Smalltalk and HyperCard
35mReviving the art of software design
42mWhat our Brains can Teach us About Software Engineering
