Live data from Hacker News

Developers are burned out, quitting jobs and creating a crisis for recruiters

worklife.news

31–40 of 130 posts

Re: Developers are burned out, quitting jobs and creating a crisis for recruiters

#32
post #5
post #4

> creating a crisis for recruiters Weird angle. Isn't the actual story the high levels of burnout in developers, rather than the inconvenience this creates for recruiters? The article is more balanced, but why lead with this?

"Won't someone please think of the recruiters!"

I know a few recruiters who made close to $1 million in fees in the past few years. I dont feel sorry for most of them

Re: Developers are burned out, quitting jobs and creating a crisis for recruiters

#33
post #15

Not a surprise. When senior devs leave an org due to mismanagement or other reasons, it creates more work for those left behind. And it's become extremely difficult to find replacement for the seniors that left. Senior devs are nowhere to be found through regular applicant pipelines. They seem to be leaving as a result of reaching out to friends/former colleagues. Also relevant: - https://news.ycombinator.com/item?id…

People really don't talk about landslide risk enough. A project with a high tech debt or operations burden is at high risk of losing enough people to zero out the project. Lose one or two people at the same time and suddenly the rest of the team is in an untenable situation. Maybe they were thinking casually about leaving before, but now that their burden has increased by 30% its more serious. Then you just keep losing people until the project fails. Can be basically impossible to restaff the project.

Re: Developers are burned out, quitting jobs and creating a crisis for recruiters

#34
post #14

It points to developer apathy. I sometimes wonder if that's just the global feeling at the moment. Everyone that's working on widget X suddenly doesn't care because of all the crises going on. Rampant inflation, extreme inequality. By continuing to work on widget x they are just supporting more of the same. Think people want society to change a bit before moving forward with being happy.

This is just intrinsic to how businesses are run.

Businesses are run by decision makers. Decision makers delegate tasks to do-ers. If do-ers mess up, it is solely their fault for underdelivering (in the eyes of the delegator/decision-maker).

The idea that do-ers can make decisions or inversely - that decision makers can do (anything beside delegate) is alien in business.

Re: Developers are burned out, quitting jobs and creating a crisis for recruiters

#35

> A report from software platform LaunchDarkly revealed that nearly 7 in 10 developers (67%) have left a job due to pressure around minimizing deployment errors or know someone who has. I'm not necessarily disagreeing with the statement, but this is a biased-as-hell source for this statement given that LaunchDarkly's product is feature-flag-management (to minimize deployment errors).

The question from LaunchDarkly, btw, was as follows (asked to "500 software developers across a range of industries and job titles"):

> Have you or someone you worked with ever left a job due to pressures from over minimizing mistakes (i.e. avoiding rollbacks or failed deployments)?[0]

...Which I also would not be comfortable summarizing as "minimizing deployment errors"

[0] https://resources.launchdarkly.com/ebooks/release-assurance-...

Re: Developers are burned out, quitting jobs and creating a crisis for recruiters

#36
post #2

Full disclosure - I work at LaunchDarkly (I look after our DevRel team) - but this is a topic I'm super passionate about also, so though it was worth sharing out. We talk about burnout a lot - but what I really appreciate about posts like this (and the report that it references) is that it gives some tangible examples of where that burnout comes from - and hopefully some paths to mitigating it. Hope you find the read…

I can confirm that, anecdotally, this is a fairly accurate portrayal of the reasons for my burnout over the last couple years.

The past several years at my company have been particularly focused on “quick and dirty results” that I predict will end badly, and so far it has every time, leaving me feeling responsible despite management decisions that ignored the consequences and recommendations I laid out. It gets old.

So, shortly before the pandemic, I took initiative to work extra nights and weekends to build a working prototype of a new version of our core internal app, that would ultimately let us go faster and would transform the way we communicate and give us unprecedented flexibility with our clients.

It was passed off as “that’s nice, but let’s get {x} out the door first”. It quickly became apparent that there was, and will always be, another {x} that needs to get out the door before we do anything else.

Having more autonomy and trust that I might actually have a solid grasp on what projects will yield the biggest returns, and being able to commit my focus to those tasks, and being able to hold my managers to the same accountability that they hold me to when making decisions, all would go a long way to improving my job satisfaction AND most importantly, improving our product and our value that we provide to our clients.

Re: Developers are burned out, quitting jobs and creating a crisis for recruiters

#37
post #20

My biggest source of burnout is really from mundane failures in processes: flaky tests that fail for no good reason, and obscure bugs that are hard to reproduce. These things take up 90% of my time and I feel like a code janitor, rather than a developer. Any company dealing with burnout should consider this.

Its also part of your job to be part of the solution and help fix them. Why are the tests flaky? Maybe you can spend a day and fix it? Obscure bugs - ok they are hard to reproduce, but if it was easy, they would probably outsource your job to some Indian developer

Re: Developers are burned out, quitting jobs and creating a crisis for recruiters

#38
Not only is there burn-out on the job, but could there also be interviewing burn-out?

In the software industry, you're doing yourself a disservice by staying at a company for more than 3 years. Even 2 years is pushing it, that is unless you are seeing wage increases that match or exceed inflation. And even if you haven't reached that amount of time, it's smart to start applying and interviewing earlier so you can have a better pick by the time you're ready to get out. I know some on HN will deny this, but I've seen enough resumes and LinkedIn profiles that demonstrate otherwise.

Hence, many of us are in a sort of medium-frequency cycle of interviewing. Applying for jobs becomes a job in and of itself, and as someone going through that process right now, I think the process has gotten much worse.

Not only are you likely to go through 3 to 4 rounds of interviews for a given employer, but now you've got to do take-home assignments. Most of the time, the estimated duration they provide is an understatement, especially if you actually want to show your best work. I've had 3 so far that wanted me to do a take-home assignment that they said could take several hours and even days. I refuse to do any that are estimated to be longer than 2 hours at this point. The other person is likely an introvert and sucks at interviewing, which can ruin your chances if they perceive the interview as not having gone well. In either case, you probably won't be hired at that place anyway.

Now multiply that experience by around 30% of the applications you've sent out. To have enough options on the table, you've got to send out at least 40+ applications (unless you've got a connection at a company already). Not only are you having to fight off all those other applicants, but you're spending a lot of your free time doing so.

Let's not forget the hours you'll also now have to spend hammering through Leetcode so you don't look like a complete fool in front of unrealistic problems you wouldn't be expected to complete in under an hour in real life.

Who actually doesn't dread facing this every few years?

I want to work in my field, but part of me also feels like saying "screw this" in favor of living in a van down by the river. Having experience might land you a better salary, but when you switch companies it's like being a junior developer all over again. I can only imagine how much it sucks for someone who has a family and kids.

Re: Developers are burned out, quitting jobs and creating a crisis for recruiters

#39

> A report from software platform LaunchDarkly revealed that nearly 7 in 10 developers (67%) have left a job due to pressure around minimizing deployment errors or know someone who has. I'm not necessarily disagreeing with the statement, but this is a biased-as-hell source for this statement given that LaunchDarkly's product is feature-flag-management (to minimize deployment errors).

The question from LaunchDarkly, btw, was as follows (asked to "500 software developers across a range of industries and job titles"): > Have you or someone you worked with ever left a job due to pressures from over minimizing mistakes (i.e. avoiding rollbacks or failed deployments)? [0] ...Which I also would not be comfortable summarizing as "minimizing deployment errors" [0] https://resources.launchdarkly.com/ebooks…

oh that is so sneaky and that would never fly in a scientific study.

Re: Developers are burned out, quitting jobs and creating a crisis for recruiters

#40
post #14

It points to developer apathy. I sometimes wonder if that's just the global feeling at the moment. Everyone that's working on widget X suddenly doesn't care because of all the crises going on. Rampant inflation, extreme inequality. By continuing to work on widget x they are just supporting more of the same. Think people want society to change a bit before moving forward with being happy.

Adjacent thread in a different market, currently at the top of r/medicine: "Is it just me... Or do things feel off?"

https://www.reddit.com/r/medicine/comments/w9ufnt/is_it_just...

Post reply on HN