Keynote: The Art of Simplicity
summary
Argues that most complexity is accidental and shows concrete fixes: replaces an error-prone imperative name loop with filter/map/join in JavaScript, demonstrates Java enum weirdness and opaque sqrt code as examples of cleverness gone wrong, recounts a failed Java tail‑call implementation later solved with an infinite stream, and uses Google’s minimalist search and circular manhole design to show simplicity reduces failures and respects users. Urges avoid cleverness and prefers readable, testable solutions over terse or over‑engineered designs.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:16Why we make things complex
- 4:31Whats not simple
- 6:04Clever solution
- 8:03Simple is not familiar
- 9:23Simple is complex
- 14:09Not everything is familiar
- 14:54Simplicity is not overengineered
- 18:23Simplicity is not terse
- 22:34What is simple
- 28:20Simplicity
- 28:30Simple fails
- 31:43Simplicity and elegance
- 35:52Avoid mutability
- 37:47Simplify
- 39:51Simple vs Complex
related talks
22mKeynote ‘The Art of Simplicity’
51mSimplicity is Not Simple
53mKeynote: Tidy First? A Daily Exercise in Empirical Design
50mIntentional Code - Minimalism in a World of Dogmatic Design
53mIntentional Code - Minimalism in a World of Dogmatic Design
58mIntentional Code - Minimalism in a World of Dogmatic Design
25mKeynote: Calm Technology: Design for the Next 50 Billion Things
37mKeynote