Burnout that occurs outside of work isn't talked about enough, maybe because it's mainly restricted to a certain kind of individual in specific kinds of fields like programming.
Programming itself can lead to burnout because it provides a promise of infinite possibilities, and some of us get fooled into thinking we are equally as capable as the code itself. This leads to time that could otherwise be spent getting in touch with our humanity instead being spent on countless side projects, many of which we secretly hope will lead to wealth and prestige. Virtually all of those projects will fail or reach a dead end; that may not seem like a big deal in your early 20s, but the realization of repeated failure and time spent in relative solitude can take it's toll once you hit your 30s. The burnout feeling occurs, not because you are doing anything functionally different from when you were addicted to code, but because the novelty eventually fades and it becomes clear how short life is. Worse yet, you may have nothing to show for all your effort. One may even have had their social skills atrophy. Burnout can have physiological components, but most of it is mental. The negative effects of having a passion for code may lead to a sense of worthlessness. Feeling like you are as insignificant as a smudge of excrement on a piece of tissue surging out to sea can be pretty demotivating.
>and some of us get fooled into thinking we are equally as capable as the code itself
IMHO burnout as a SW dev isn't because of the coding itself, I find that the easiest part to deal with.
It's the constant pressure to stay up to date an an industry that changes faster and faster and a job market that get more and more competitive. It's the constant sprinting towards more and more ambitious arbitrary deadlines set by sales or management using half-assed Agile and Scrum processes imposed onto you by clueless higher-ups. It's constant interruptions and multitasking in several tools you have to keep up with throughout the day: chats, calls, emails, Jira, etc. while also being expected to focus and code. It's the exhausting and time consuming interview practices. It's the idiotic and overpaid management and execs who treat you like a disposable resource and thinks colorful beanbags, ping-pong and foosball tables would make me want to spend 2h commuting to the office every day to sit in a noisy open office with a view of a concrete parking lot, and that pictures of employees in funny situations with moustaches drawn on them and turned into memes and plastered around the office means a "friendly" atmosphere and it's what I would enjoy instead of WFH in peace and quiet (maybe I'm too old or something but I can't stand my workplace treating me, a professional in my 30's, like I'm a childish toddler looking to join some kindergarten playground).
Coding and debugging alone is very pleasant for me, it's why I became a dev, but it's everything else related to this industry that breaks my will to live.
On my most cynical days all I see agile/scrum used for is a selfish tool to appease stakeholders anxiety that their directives are being worked on by the demanded date and to give the micromanaging admin types something to do. It seems to effectively transfer the stakeholder level anxiety directly onto the people doing the work.
Also you’re not “too old.” It’s called wisdom to see through the emotional manipulation for what it is. That clarity can be punishing when you don’t want to just go along with it and the toxic positivity pushed in the corporate world.
Agree 100%. My old workplace is making everyone commute to office next week so that they can “team bond and destress” by playing with office-provided toys. Really. It’s so patronising and I hate the control bosses think they have over your entire life and personality instead of just your work output.
My current job let me WFH the past couple years but now they're insisting I do the 2H+ commute again four days a week once my current project ends, and I don't think I'm going to be able to manage it long (and the office culture is exactly what you've described).
If they put me on another project I can WFH from after a few weeks, I'll stick around at least a bit longer, but I don't think I'll last if they keep expecting me to go to the office. Tech job recession be damned, I'll eat some of my savings and sit out for a few months until I find something else if I must, as much as I hate that idea.
But even that I expect will still have a lot of that bullshit you're mentioning.
I don't have a problem with coding itself, I'm having fun still working on my game in my spare time, relaxing in a quiet room at a library, but in a corporate environment my brain just feels so fractured and distracted and the projects don't really hold any interest to me.
> Burnout that occurs outside of work isn't talked about enough, maybe because it's mainly restricted to a certain kind of individual in specific kinds of fields like programming.
Wish that was true. There is an outside-work burnout that's arguably quite common in society these days, and mostly not talked about either: having kids. People who are not parents themselves, and not close with some parents of small children, they won't understand. Parents just exchange knowing glances. At least those who aren't conditioned by their society/environment to pretend everything is great and child-rearing is the Greatest Privilege and the Most Rewarding Experience in the Universe.
Going through that right now, I pretty much gave up on coding after work. I tried, telling myself that side projects are keeping me sane. True or not, the tension created by not actually being able to do them, was worse. All the things you write in the second paragraph are true - and they only get worse once you're running on negative me-time budget :).
(EDIT: At least the topic of postpartum depression has been gaining some attention these days. A case of one can easily have negative effect on multiple people across a generation, and there's still very little advance warning or support given for new mothers.)
Programming itself can lead to burnout because it provides a promise of infinite possibilities, and some of us get fooled into thinking we are equally as capable as the code itself. This leads to time that could otherwise be spent getting in touch with our humanity instead being spent on countless side projects, many of which we secretly hope will lead to wealth and prestige. Virtually all of those projects will fail or reach a dead end; that may not seem like a big deal in your early 20s, but the realization of repeated failure and time spent in relative solitude can take it's toll once you hit your 30s. The burnout feeling occurs, not because you are doing anything functionally different from when you were addicted to code, but because the novelty eventually fades and it becomes clear how short life is. Worse yet, you may have nothing to show for all your effort. One may even have had their social skills atrophy. Burnout can have physiological components, but most of it is mental. The negative effects of having a passion for code may lead to a sense of worthlessness. Feeling like you are as insignificant as a smudge of excrement on a piece of tissue surging out to sea can be pretty demotivating.