Worse Is Better, for Better or for Worse
summary
Argues that narrower, rock‑solid designs beat “complete” ones by example: the original wiki in 200 lines of Perl proves tiny, extendable code spreads; 1995 PHP napkin and C’s evolution show success from reduced scope and ecosystem respect; Unix and the browser+JS story show performance and interoperability matter more than purity. Recommends shipping a fast, small, bug‑free core, iterating (30‑day → two‑week rhythms noted), and accepting throwaway refactors rather than piling on completeness.
AI-written summary · about
chapters (25)
- 0:00Intro
- 5:20Worse Is Better
- 9:30Contrasting Design
- 12:53Characteristics of Worse
- 15:33Parallel
- 16:21Performance
- 18:06Memory
- 18:48The Endowment Effect
- 20:29Respect the Ecosystem
- 25:29PHP
- 27:11C
- 28:22Objective C
- 31:23Beauty
- 32:14ObjectOriented Programming
- 33:44Fractions
- 35:57Smalltalk
- 37:17Pure Object Model
- 38:35ObjectOriented Programming in Java
- 39:18Component Object Model
- 41:18Lisp
- 42:08Algol
- 44:09JavaScript Linux
- 46:16UNIX
- 55:28Giving Up
- 56:29Conclusion
