3 ms·
The way I interpret burnout is a disconnect between how much effort you're putting in and what you're getting out of it. When your brain catches on to this disc
by SaberTail 3y ago
The way I interpret burnout is a disconnect between how much effort you're putting in and what you're getting out of it. When your brain catches on to this disconnect, it gets less and less willing to put in the effort.
If your job is actually making a physical thing, it's very easy to see the results of your work. There are tangible objects you can see and touch. Even if you're digging ditches all day, you can see the holes. In software, you're producing something intangible, and so it's much harder for your brain to tell you accomplished anything for all your work.
On top of this, software is cheap to iterate on. This means requirements can shift on very short notice, and the thing you built yesterday may not be useful anymore, and gets thrown in the trash. Again, your brain takes this as you putting in work and not accomplishing anything.
And then when it comes to deadlines, a lot of the time they're completely arbitrary. Someone circled a date on the calendar. Or bosses often don't do a good job of conveying why the deadline was set. Or the deadline passes and other teams aren't ready, so it turns out you didn't need to work that hard. Your brain ends up wondering why you put in all the effort when you could have done it less intensely and gotten to the same outcome.
All jobs can have aspects of these things, but I think they're much more prevalent and concentrated in software. I don't think there are any magic bullets. Maybe if managers and bosses understood this and took some care to not exacerbate those types of situations that contribute to burnout. Make sure people understand what they're contributing and give them something they can point to. If something gets canned, try to give the engineer a quick "win" with a small project before putting them on something new that might also get cancelled. Make sure deadlines aren't arbitrary and ideally that they can be met without grinding.
- stevage 3y agoYeah that's a great summary. Not a magic bullet but it helps to build your own mental defenses to this. Recognise that the deadline is arbitrary. Predict what will happen when it arrives. Adjust your effort so you are not overextended time and again. Similarly recognise when code is likely to be thrown out, and don't pour your heart and soul into it. Make it good enough, then look for you life satisfaction elsewhere.
- gowld 3y agoSoftware is plenty tangible, if you understand software, which you do if you create it. The disconnect comes from building and building and building and never launching, or getting cancelled.
- deleted 3y ago[deleted]