Good or bad - a key skill for developers
summary
Argues humans systematically misjudge what’s good versus popular, backing it with numbers: 400 million iPods and 2 billion iPhones sold, and claims Apple removes features (no copy/paste, no Flash) to prioritize smooth UX (half the engineering effort tuning input responsiveness). Shows PHP’s tradeoffs: no threads or monkey‑patching but a shared nothing model that simplifies deployment and debug iteration. Recommends writing decision rationales (example: yarn vs npm), automating deploys, and making debugging instantly available via separate Xdebug containers.
AI-written summary · about
chapters (11)
- 0:00Start
- 10:41PHP keeps old 'bad designs English keeps old spellings
- 13:20PHP lacks: Monkey-patching
- 14:32Lack of consistency
- 18:12Features generally make things harder to use.
- 21:20iPhone lacked features but had great ease of use
- 22:24PHP has great ease of use
- 28:56Learn new aesthetics - Kintsugi
- 33:59What JS build tool should we use?
- 36:34Individuals value features over 'ease of use
- 38:30Choices for 'ease of use
