How to NOT go insane after 20 years as a dev
summary
A twenty-year software developer reflects on why many colleagues left coding for management or burned out despite programming becoming technically easier. The talk names burnout and depression as problems and shares the speaker's personal habits, practices, and lessons that helped them stay healthy and happy in a developer role over two decades, with the goal of giving concrete, experience-based tips so others can avoid leaving hands-on development.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:32Depression and burnout aren't your fault
- 10:12Brain model for programmers
- 23:37Emotions and signals
- 34:48Handling frustration and anger
- 41:48Managing fear in IT
- 46:19Survival in tough environments
- 53:18Tech and self-understanding future
related talks
53mHow to NOT Go Insane After 20+ Years as a Dev
49mWhy Developers Quit
34m40+ and still coding? Make the most of your experience
37mHow to Survive the Burnout
44mAvoiding Burnout as a Developer: Practical Steps and Tools
39mPreventing Developer Burnout
26mAll the things I learnt as a junior developer (so you don't have to)
40mDev (depresiya) Ops