Get old, go slow, write code!
summary
Claim: getting older and deliberately slowing down improves long‑term velocity and retention. Data: Stack Overflow: avg age 28 and developers expect to stay 8 years before leaving; >50% report deadline stress and cutting quality. Examples: building a new Swedish tax login is delayed a year and results in maintainable, long‑lasting software; marathoner Ricardo Abad illustrates sustainable pacing. Practices shown: daily planning, refactoring and Boy Scout rule, book clubs and code katas, adding slack to avoid rushed, low‑quality releases.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:57Aging as a developer
- 7:15Audience age and experience
- 13:41Why devs quit early
- 18:23Reasons developers leave
- 23:21Peter Principle in tech
- 26:18Slow down in development
- 31:05Quality over deadlines
- 37:50Cost of rushing
- 40:50Stress and quality poll
- 41:10Slow down and improve
- 43:50Processes and team dynamics
- 45:58Planning and standups
- 47:23Refactoring and tech debt
- 48:27Add slack to avoid burnout
- 50:13Final poll and call to action
- 51:18Closing advice
related talks
47mGet old, go slow, write code!
38mGet old, go slow, write code!
45mGrowing old gracefully: on being a career programmer.
18m“47 Years Old: They Still Haven't Noticed …”
52mSlow Life or How to Live Well as a Developer
15mIt's Never Too Late to Become Junior Again
34m40+ and still coding? Make the most of your experience
36mSenior Developer Development