Why Developers Quit
summary
Argues developers quit when esteem and self‑actualization vanish, not because of topic boredom, and shows remedies: shipping more, run retrospectives that celebrate wins, practice deep practice under feedback, and hire a dedicated coach who prioritizes empathy, organization and coaching skill over raw coding. Gives concrete practices—pairing with designers, code retreat constraints, algorithms like A (used while cloning Warcraft in Ruby), simulating hardware in Ruby—and launches a program to coach 24 people mentorship* into conference speakers with proposal help and travel support.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:33Why Developers Quit
- 2:57The Long Game
- 6:01Developing Happiness
- 8:49How Do You Reflect on Your Work
- 11:04Managers
- 14:08Self-Actualization
- 15:09Becoming a Programmer
- 15:37How Did You Become a Programmer
- 16:57Windows 95
- 28:07Goal of Deep Practice
- 30:55Code under Constraint
- 31:38Refactoring Existing Code
- 32:17Teaching and Mentoring
- 34:14Error Driven Development
related talks
26mQuit Your Job. Srsly.
18mThe Art and Science of Thriving Developers: 7 Key Strategies
31mThe Effective Developer - Work Smarter, Not Harder
36mI quit with tech and you should too
33mHow to Enhance the Skills of Experienced Developers
57mHow to NOT go insane after 20 years as a dev
50mThe Effective Developer - Work Smarter, Not Harder
10mA great developer - how to be one, how to find one?