The Developer Rhapsody
summary
Argues that individual developer productivity metrics are harmful and easy to game, citing the Twitter lines-of-code firing rumor and McKinsey’s claimed 20–30% fewer defects, 20% better employee scores, 60pp customer satisfaction which the speaker doubts. Recommends team practices that actually work: mob/programming and pair work, frequent CI/CD with auto-deploy every merge so rollbacks are simple, and treating LLMs as helpers for prototyping not architecture. Advocates being adaptable — be the bicycle repairman — and values steady, long-term contributors.
AI-written summary · about
chapters (12)
- 0:00Welcome
- 1:28From dev to Google
- 6:25Recession cuts productivity myths
- 10:19Measuring productivity fails
- 13:53Team’s bicycle repairman
- 17:14Mistakes worse than chef’s slip
- 20:27Quality over firefighting
- 25:45AI stealing developer jobs?
- 30:48Career role model
- 35:43Are you a role model?
- 41:08In praise of mediocre devs
- 50:43Applause for unsung heroes
