I quit with tech and you should too
summary
A long‑time dev quits after 20 years and claims it’s the best career move, trading code for coaching and better mental health; specifics include working as a route setter for €10 per hour, paying rent €1,700, taking a year and a half sabbatical, trying to open a climbing‑gym plan that fails due to bureaucracy and an unreliable partner, then landing a non‑coding role at Boolean helping students switch careers — concrete numbers, failures, and outcomes, not platitudes.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:06Early passion for programming
- 3:14Passion versus work-life balance
- 5:21Ownership pressure and burnout
- 7:10Tech as a means to impact
- 8:16Toxic tech communities
- 10:06Company culture and burnout signs
- 12:14Quitting tech for sabbatical
- 14:50Moving to Barcelona and challenges
- 17:01Facing failure and alternatives
- 19:10New role and full circle
- 19:56Mental health and burnout signals
- 21:00Overcoming excuses to quit
- 23:10Encouragement to quit tech
- 23:55Q&A
- 24:41Coding after quitting
- 25:23Career shifts in tech vs quitting
- 26:06Losing purpose in tech
- 27:10Why start a developer journey
- 27:52Age and passion shifts
- 28:59Big companies and purpose
- 30:27Love-hate relationship with tech
- 31:29Avoiding burnout without quitting
- 32:55Risk of returning to tech
- 34:00Big corporations and web ethos
