Another burnout post
Burnout in software engineering is described as a mix of mental exhaustion, loss of meaning, and frustration with corporate structures that turn a once-beloved hobby into pressured, goal-less ticket work. Commenters contrast self-directed “lone wolf” projects with jobs dominated by meetings, opaque codebases, and interchangeable roles, and debate whether the problem is programming itself, the type of company, or broader work culture and personality fit. Many suggest coping strategies—reduced hours, stronger boundaries, changing domains, or switching careers altogether—while others argue that fulfilling, impactful programming roles do exist but are harder to find.
Nature of burnout in software work
- Many describe burnout as mental exhaustion where thinking itself becomes hard, distinct from just “work being not fun.”
- Several report repeated or long-term burnout, with recovery taking months and sometimes leading to aversion to job listings and interviews.
- Key stressors: constant context switching, meetings, deadlines, on‑call, and feeling “always on” even off-hours.
- Some argue most programming tasks are not uniquely demanding vs other white‑collar jobs; others insist IT’s “always‑on” culture makes it especially draining.
Hobby vs professional programming
- Strong theme: programming is enjoyable as a self-directed hobby but becomes stifling as a job with tickets, managers, and imposed tech stacks.
- Loss of autonomy and creative ownership is central; Jira tickets feel endless and interchangeable.
- “Lone wolf” / “code hermit” work is contrasted with team-based corporate development full of coordination and politics.
- Some realize they like problem-solving and design, not “writing code” per se, and feel better when they move into roles with more design/architecture or product focus.
Agency, meaning, and job fit
- One camp says: you have agency; seek “real products for real people,” mission-driven orgs, or domains like healthcare, embedded, or research.
- Others counter: many software jobs are low-impact (ads, CRUD apps), equity and direction are out of reach, and not everyone can just “go part-time” or switch fields.
- Comparisons to medicine/psychotherapy highlight how meaning can offset grind; some think most software roles lack that.
Coping strategies and alternatives
- Tactics that helped: switching teams, 4‑day weeks (32 hours), strict “no overtime/weekends,” monotasking, outdoor exercise, long walks, new hobbies.
- Several take 6–12 month sabbaticals between jobs; some see their desire to code return, others fear it won’t.
- A few leave or plan to leave software entirely (truck driving, sailing, other “simpler” work).
Critiques of the original post
- Some find the post relatable and praise its honesty; others see it as preachy, self‑centered, and dismissive of other professions’ suffering.
- The blanket claim that working for others in software is “soul-destroying” is disputed by developers who enjoy long careers in the field.
- The digressions into “ancestral food,” footwear, and jaw/tongue posture are viewed as eccentric or unconvincing by many.