I believe the disconnect is that people don't view developers as builders. You wouldn't expect to call your general contractor four months into a house build and ask to turn it into a skating rinkâwhile keeping the same cost and timeline.
Prime on healthygamer would be an amazing collab tbh
The reason devs keep buring out because non-technical people are DELUSIONAL. Today I seen a podcast where dude said "I know 5 companies completely controlled by AI, without humans". This is what raises your bars - delusion of people who creates requirements for your work.
âWhy didnt you finish this ticketâ âBecause I had 5 hrs of these meetings and 3 hrs of interruptions from messagesâ
No matter how hard you work, your manager will tell you that you need to work harder. No matter how hard you try to keep up, the industry makes you feel like you don't know the right tech. You are judged by some mistake you made, not the effort you put into delivering so much for your job. I witnessed a new coworker who got hired for JAVA and his team forced him to build an app using JS.
38:30 The "we'll get you a subscription to a mindfulness app" is so real it actually triggered a fight or flight response when I heard it.
I love programming. I hate dealing with the people around programming. I've walked away from volunteer projects because the people involved were terrible. Abandoning paying work is harder, but often necessary. Remember, you're often working for people who typically don't understand your job, but then don't trust your expertise. Just try to get permission to devote the man hours needed for a proper security audit of software updates and you'll see what the higher ups actually think of you. This is why we have gasoline dispensers that take 2 seconds to accept a single character input.
We use powers of two for our estimating, but we do actually translate them into time: 1=hours, 2=days, 4=weeks, 8=months (which means break it apart). The point isn't to say when specifically something is going to be done. The point is to be able to prioritize and get a rough idea of if its worth it.
Another difference is that a Dev is almost always building something NEW, and the timeline is at best just a decent guess.
Can't speak for everyone, but in my personal experience, burnout happens for the following reason: absolutely no reward for a job well-done. The reward for completed work is more work. As someone with ADHD, the reward systems in my brain respond to that cycle as punishment rather than reward, and I emotionally find myself reacting to it like I'm being punished for finishing work, which makes me want to escape rather than continue working on the next thing. There's no incentive, no recognition, no ability to present findings or see how my work is making an impact on others. Also, I don't originally come from a CS background, and trying to communicate in the tech world is absolutely infuriating. Nobody knows how to communicate like human beings, and if I didn't have experiences outside of tech to compare it to, I'd internalize it as my own problem. It's not. The industry is full of empty communication and fighting tooth-and-nail to get direct answers to simple questions. Third, working in tech is not a job that is condusive to healthy habits. It isn't that you CAN'T live a healthy life working in tech, but you have to go out of your way to stay healthy, since most of your day is spent staring at screens, sitting down, and being made to feel like taking breaks is being lazy. I love pair-programming, but I have certain colleagues who I absolutely hate pair programming with because they take a meeting that is scheduled for 30-60 minutes and turn it into a 2.5 hour coding marathon where by the end of it, I can't focus on anything and I feel defeated and resentful since I didn't get 5 minutes to process at any point. The biggest pain-point in my opinion is that none of these burnout factors that I've mentioned need to be pain points. There are reasonable accomodations, workflow changes, and communication strategies that can fix all of them, and I know this because I've worked in environments that allow me to thrive in the past where these simply aren't issues. There are reasonable fixes--fixes that I've vocally suggested on more than one occassion--and yet the answer is always, "I hear you. I understand you. But have you considered that maybe you need to use a day of PTO now and then to recharge your batteries?"
1:26 "THE SOURCE OF THIS DATA WAS RANDALL'S BEHIND!" đ
Have 5 bosses, none of them understand the words coming out of my mouth and the one that does doesn't care. At least that was what burned me out.
If you have a PM close to mine you have to explain the same issues multiple times, make final decisions and manage your tickets, all while they are the ones who gets rewarded.
For me itâs always time pressure. My work rate doesnât increase when some manager decides to cut my evidence based schedule in half, all it does is spike my stress level.
If you haven't worked on an under budget, undersold project without a proper scoped out requirement and the requirements double while you're working on the feature and the timeline cannot be reset you got no idea
The craziest thing about the agile poker way of estimating hours is I've never seen a "get sick", "took time off", "life events" task added to scrum. So when the obvious thing of people having lives and being human came up, it always was a shock to the schedule somehow Like it always had to be a sprint in advance planning, and treated like a huge surprising burden
âThe Programmersâ Credo: we do these things not because they are easy, but because we thought they were going to be easy.â
Iâm burning out because sales promised piece tracking to customers and iâm one of the few that realize and accept that weâre 20-30 years away from actualized piece tracking at this pace
This was really good, dude was funny and smart. And therapy is often just having someone who is willing to listen to you, but who has no emotional investment in your issues one way or another, and who ultimately is both affirming you and guiding you to think through and confront what you either haven't been able to bring to the surface or what you have been actively avoiding (a more sophisticated version of calling you on your own bullshit).
@HealthyGamerGG