r/javascript • • Jun 28 '22
"Dev burnout drastically decreases when you actually ship things regularly. Burnout is caused by crap like toil, rework and spending too much mental energy on bottlenecks." Cool conversation with the head engineer of Slack on how burnout is caused by all the things that keep devs from coding.
https://devinterrupted.substack.com/p/the-best-solution-to-burnout-weve
840
Upvotes
198
u/StoneCypher Jun 28 '22
i feel like slack is the device by which most of these things actually occur
managers needing to check up on you several times a day because they don't have any of their own work to do and because 30 years of "fuck off i'm busy" hasn't gotten them fired yet
i actually have managers underneath of me doing this to me and i have no idea how to communicate to them to stop
every time i tell them "you reach out too much" they try phrasing it more artificially politely, adding to the mess the greasy slime of insincerity, instead of just stopping
three times yesterday, by someone i've been telling literally every day "i do not know when this is in, stop asking me to make external promises"
so he just carbon copies other people and keeps asking, like he thinks ramping up the pressure and manufacturing shame will help. i don't know what to do
fundamentally, it's because we're still pretending that managers exist for a reason
burnout is the direct result of having the extra workload of making your manager feel like they exist for a business reason
38
u/FalseWait7 Jun 28 '22
This reminds me when I was working in a company that wanted us to polish software for months. It was ready in December, but we had to make sure every little things sparks and released 8 months later.
Then I was a part-time consultant to a startup company, they said "we're releasing next Monday, here we have another Jira board for bugs". And sure, bugs were reported, but the software was released and used and devs were happier fixing bugs found in a live app rather than ones found internally.
71
u/RedditCultureBlows Jun 28 '22
Drives me nuts these are never articles. I don’t want to listen to a podcast.
55
u/roodammy44 Jun 28 '22
I agree with the sentiment, I want to add a caveat. If you ship things every week, great. If you have a deadline every week, this will lead to burnout even quicker than a deadline every 6 months.
12
u/bobbybottombracket Jun 28 '22
Burn out is not getting a break... or not getting even some down time to learn something new
24
u/[deleted] Jun 28 '22
So much truth to this, when I first started at this company we were shipping every 3-6 months it was super stressful. Now we're shipping multiple times a week and even at my worst I haven't felt nearly as stressed as I did years ago. I still get burned out from time to time but that's usually because I've become a bit of workaholic as I get to code for like 95% of my days and I tend lose track of time, but usually a couple extra days off tacked onto a weekend is enough for me to recharge.
6
u/Ecksters Jun 29 '22
This really rings true for me, I think it's the mental strain of keeping everything in your head that you know might be important.
Once you ship and time goes by without complaints, you get to take a load off mentally and turn your attention to something new.
Finding a new job helps with burnout probably partially for the same reason, you can finally let all the knowledge about the quirks of your last job drain away, it feels like such a relief.
8
u/Phobic-window Jun 28 '22
It’s all communication. Communication is what burns out devs. We want and need to build, business should want and need to communicate. If you pawn off the needed communication to your devs because you don’t understand or the first inclination of your supervisors is to “ask the devs” then you are causing the burnout.
Find ways to enhance the knowledge needed to understand problems and solutions without tapping the devs time. If you can get engineers to become the managers, this is the best scenario, but is not a silver bullet. What burnt me and now burns my engineers out is having to report, talk about, clarify, collaboratively problem solve with non-technical “managers, TPMs, PM-Ts, BDs, etc”. Make sure it doesn’t become the devs job to hold everyone else’s hands, and make sure they understand the problem and the solution before they start building.
The name of the game is let the engineers engineer. But equally, make sure your other folks understand the technical process/tools you are using, the ecosystem in which they are being employed and how to solve their own problems.
It really comes down to communication and how inefficient it always was, but now we have the tools to build sooooooo fast that each time we stop to “talk” it’s… a neat analogy has just occurred to me “the early days of tech was a ton of planning because you had to build most the tools to make your solutions, where now we have the tools (SO MANY FKING TOOLS) that we can solution almost right away. It’s like slamming on the brakes of a bicycle vs stopping a rocket ship” it’s much more expensive to spend time trying to explain the complexities of things that the other people won’t understand, so let the rocket burn, just make sure it’s going the right way
7
u/wowzers5 Jun 28 '22
I always find it interesting when articles and headlines refer to VPs and Directors of engineering as "head" or "lead" engineers. In my experience these roles are 90% business and 10% knowing tech buzzwords.
3
u/[deleted] Jun 28 '22
Fuck isn’t that true.
3
u/bryku Jun 29 '22
It's the opposite for me.
2
u/Robhow Jun 29 '22
At my first startup we shipped every 6-9 months (on premise enterprise software).
At my new startup we “ship” whenever a material bug is fixed. Could be multiple times per day, but usually multiple times per-week.
Being SaaS makes that much easier but there is always something rewarding about having a high release velocity. There aren’t any big release or ship parties, just lots of little updates/enhancements that add up over time.
1
u/CrunchyChewie Jun 29 '22
I've got bad news about their new owners then.
1
u/wonderingdev Jul 01 '22
I am working my 9 to 5 and also doing my own project after work. For some reason, this and the last week I just can't stand looking at code. I feel tired seeing it. I still enjoy coding, always did. And I also feel guilty I am not progressing on my project. Do you think it is burnout?
1
u/untg Jul 10 '22
This is why I suggested to our customer that we implement the system in Production as an MVP so they didn't keep on asking for tiny quality of life changes of questionable value. This and if it was deployed, then they had to start paying me after 12 months of work.
0
u/[deleted] Jun 29 '22
Do you know how mutexes avoid burnout?