Stack Overflow Survey: 80% of developers are unhappy
Stack Overflow Survey: 80% of developers are unhappy
This year, as expected, the main topics in the Stack Overflow survey were use of AI and dissatisfaction in the workplace.
So is 80% of everyone else making 50k less a year.
Maybe it is just my experience, but in the last decade, employers stopped trying to recruit and retain top developers.
I have been a full time software engineer for more than a decade. In the 2010s, the mindset at tech giants seemed to be that they had to hire the best developers and do everything they could to keep them. The easiest way to do both was to be the best employer around. For example, Google had 20% time, many companies offered paid sabbaticals after so many years, and every office had catering once a week (if not a free cafeteria). That way, employees would be telling all of their friends how great it is to work for you and if they decide to look for other work, they would have to give up their cushy benefits.
Then, a few years before the pandemic, my employer switched to a different health insurance company and got the expected wave of complaints (the price of this drug went up, my doctor is not covered). HR responded with "our benefits package is above industry averages". That is a refrain I have been hearing since, even after switching employers. The company is not trying to be the best employer that everyone wants to work at, they just want to be above average. They are saying "go ahead and look for another employer, but they are probably going to be just as bad".
Obviously, this is just my view, so it is very possible that I have just been unlucky with my employers.
I've kinda checked out of the private sector for this reason. I've been having a great time working for a government job. Great benefits, union, etc... pay is about 80 percent of what others make but it's more than enough to get by.
In the 2010s, the mindset at tech giants seemed to be that they had to hire the best developers and do everything they could to keep them.
Not really. The mindset was actually to hire skilled developers just to dry up the market, so that their competitors would not have skilled labour to develop their own competing products and services.
Then the economy started to take a turn for the worse, and these same companies noted that not only they could not afford blocking their competitors from hiring people but also neither did their competitors. Twice the reasons to shed headcount.
It was not a coincidence that we saw all FANGs shed people at around the same time.
I feel blessed that I like my current job. Good manager, interesting work, limited amounts of bureaucracy. Most of this is a lucky coincidence but there are some things we can do. I had to explain many times to people which tasks I'm good at and which ones they should ask other people to do. I regularly defend this position. I set aside the morning for creative work only, no meetings, no admin, just thinking and solving. In the afternoon I down tools and do something physical, outside in daylight. A regular sleep cycle is absolutely critical for the maintenance of health and mood. Fresh food and companionship. Regular meditation. Do the basics well. These are the things that have made me happy.
Do you have kids? Does your schedule accomodate parenting and chore duties? I feel that after my kid was born, I lost the possibility of having a good night of sleep. And my kid is already older, so I don't have the issue of waking up many times during the night anymore. Even so, just surviving has been difficult.
Sounds like you're well paid and your time is valued, I imagine most devs would be happy with that!
I would say 80% of employees are unhappy, but I don't have any data to back this up.
Every job lately seems to have been infected by Meta/google "data driven" leadership. Its so painful and wasteful sometimes.
Every job lately seems to have been infected by Meta/google “data driven” leadership. Its so painful and wasteful sometimes.
It's cargo cult mentality. They look at FANGs and see them as success stories, and thus they try to be successful by mimicking visible aspects of FANG's way of doing things, regardless of having the same context or even making sense.
I once interviewed for a big name non-FANG web-scale service provider whose recruiter bragged about their 7-round interview process. When I asked why on earth they need 7 rounds of interviews, the recruiter said they optimized the process down from the 12 rounds of interviews they did in the past, and they do it because that's what FANGs do. Except FANGs do typically 4, with the last being an on-site.
But they did 7, because FANGs. Disregard "why".
Yeah. I, like most leaders, spent some time learning all that crap. It was awful and worse than useless.
Google and Meta's secrets are recruiting top talent to for top dollars, and then buying every start up that threatens their empire. There's no secrets to great management to be had there.
I just threw out my copy of "product engineering at Google".
Can confirm. Was quite unhappy in my mechanical engineering job, had an opportunity to develop something nice in python, was told we'd do it in excel/vba instead, still unhappy.
Nice. You can put that on your resume so you can get more of those kinds of jobs.
(/s. I like excel to a point but i really feel your pain too-- and fuck vba)oh no...
Or maybe 80% of people are unhappy. No data here either
80% seems too high, but the US Surgeon General declared a loneliness epidemic https://www.hhs.gov/sites/default/files/surgeon-general-social-connection-advisory.pdf
And Gallup claims that 29% of Americans have been diagnosed with depression at one point: https://news.gallup.com/poll/505745/depression-rates-reach-new-highs.aspx
So... That is not good. It is almost like humans evolved to live in tight knit, walkable communities.
80% of beings in the multiverse
Technical debt is the number one cause of developer frustration. Working with imperfect systems demoralizes programmers, making it difficult to do quality work.
I'd wager not being given time to tackle technical debt is indeed frustating...
I feel burnt out on professional development, but at least for me tech debt is not the issue. Everything is imperfect after a while, because requirements change all the time and overall it's not me accruing the debt. That's why I don't care.
I keep seeing a pattern of sre/devops/sysadmin tasks being given back to developers and canning the SREs. Hard to understand why. Then some of the SWE get stuck basically focussing on infra SRE stuff and become unwilling SRE more or less. Circle of life? Do the old devops folks get made into glue or something?
"Devops" original intent meant you don't have a separate "operations" department separate from teams "developing" your product / software due to competing incentives. "Dev" wants to push new stuff out faster; "ops" wants to keep things stable. Or "dev" needs more resources; but "ops" blocks or doesn't scale the same. The idea was to combine both "dev" and "ops" people onto projects to balance these incentives.
Then managers and cloud clowns repurposed it to apply to every person in a project so now every member is expected to perform both roles (badly). Or even more overloaded to somehow refer to "developer infrastructure" teams.
The secret is just to do it anyway. I have yet to work in a job where anyone actively stopped me fixing technical debt, even if they never asked me to do it.
Use overestimation padding, eh?
Depends on the work load. The company should make time for that and you should get paid for it.
I don't care what your fancy RAMrod doohickeys say Johnson! We need that system up tomorrow so we can reach our quarterly earning projections for the shareholder's meeting!
My boss legit says that he will give me some time to work on it every 2-3 months and then drops a “customer requires X feature and I promised that we will deliver in one week”. And mind you we have to patch up to 3 major versions in the past to back port the new feature because client haven’t upgraded and won’t in near future… which means sometimes our major releases are 60-70% same as our minor patches for old versions. Semvering much?
Yeah, that's probably more the issue. We've seen too many times throwaway code become production code because "it works already, we need to move forward".
It is. Source: We've had the same issues for years, but never get any time allotted to fix them.
Yay, horror story time!
Will AI steal their jobs? 70% of professional programmers don’t see artificial intelligence as a threat to their work.
If your job can be replaced with GPT, you had a bullshit job to begin with.
What so many people don't understand is that writing code is only a small part of the job. Figuring out what code to write is where most of the effort goes. That, and massaging the egos of management/the C-suite if you're a senior.
Automation is always incremental.
I'm an accountant. Components of the job have been being automated or systemised for many decades. Most of the tasks that occupied a graduate when I was one 20 years ago don't exist anymore.
Not because AI is doing those tasks but just because everything became more integrated, we configure and manage the flow of data rather than making the data, you might say.
If you had to hire 100 professional programmers in the past, but then AI makes programmers 10% more efficient than previously, then you can do the same work with 91 programmers.
That doesn't mean that 9 people were doing something that an LLM can do, it just means that more work is being completed with fewer programmers.
If you had to hire 100 professional programmers in the past, but then AI makes programmers 10% more efficient than previously, then you can do the same work with 91 programmers.
You've nailed to root of the misunderstanding by non-programmers. We're already optimized past that target.
Some people think we type all day. We don't. We stare at our screen saying "what the fuck?!" for most of the day. Those is especially true for the best programmers doing really interesting work.
There's maybe three living humans who actually know how to correctly build a Windows installer. One of those three is paid to sell software to automate the task for everyone else. The other two retired already. (One is hiding out as a bar tender and claims to not speak any English if recognized from their MSI days.)
Pick an interesting topic in programming, and you'll find similarly ludicrous optimization.
There's a few hundred programmers building all banking automation, selling it to millions of bank employees.
It's possible that AI will force a dozen people to stop doing banking automation. It's a lot more likely that the backlog of unmet banking automation need will instead just get very slightly smaller.
Now, the reality of the economics won't stop CIOs from laying off staff and betting that AI will magically expand to fill the gap. We're seeing that now. That's called the "fuck around" phase.
But we've seen "this revolutionary technology will make us not need more programmers" before (several times). The outcomes, when the dust settles are:
- The job is now genuinely easier to do, at least for beginners. (Senior professionals had access to equivalent solutions, before everyone else got excited.)
- More people are now programmers. (We laid a bunch of them off, and we meant to not hire any back, but it turned out that our backlog of cool/revolutionary/necessary ideas was more important to leadership than pinching pennies.)
- A lot of work that was previously ignored completely now gets done, but done very badly by brand new programmers. (We asked the senior developers to do it, but they said "Fuck you, that's not important, make the new kid do it." I think they're just still cranky that we spent three years laying off staff instead of training...)
- The average quality of all software is now a bit worse, but there's a lot more variety of (worse) software now available.
But that is always happening. Software that now can be built by two programers needed IBM few decades ago, just because of hardware, languages, available libraries and shared knowledge.
But we still have so many "app ideas" that there is more work to be done. I would be happy to have AI write all those apps that I need and have no time or money to make them.
My conclusion is that it is only about money and economy. We are in unofficial recession so everyone is cutting costs, as soon as money comes back we will go back into bulking/exploration phase.
To add on this, this doesn't necessarily mean that there are fewer programing jobs in total. If people work 10% more efficently, that means that the cost of labor is only 91% of what it was before meaning that people might be able to afford to finance more programing projects. One thing that does matter is for example things like entry level jobs disappearing or the nature of the work changing. Doing less boring gruntwork can make the job more fun, but otoh digitization sometimes results in the worker having less agency in what they do since they have to fit everything into a possibly inflexible digital system.
If your job can be replaced with GPT, you had a bullshit job to begin with.
This one's funny to me, because the people who WILL try to replace you with GPT don't care if they CAN replace you with GPT. They just will.
Look at how it's haphazardly shoved into everything for no reason whatsoever already.
If all you bring to the job is looking shit up and telling me yes or no instead of actually trying to help me find solutions, or explaining me what I did wrong, you're just a glorified robot. You're in line for replacement and you'll fucking deserve it. At least that's what I wanna say to "the computer said" people.
There's a lot of like management being like "we gotta hit this deadline (that we made up)" combined with "if I hit all my targets and put in some overtime, the boss can buy another sports car this year"
I don't want to work extra to make someone else richer. Maybe if I had a shit load of shares. Maybe. But I don't. So I do my job with professional standards, but I'm not doing 12 hour days
So, roughly 20% of developers have found the right mix of self-medication?
I’ve been programming for years, I’ve only happy when working on my own stuff. It’s like the difference between renting and owning
I've rented my whole adult life, and I don't mind it. There are downsides, but owning has them too.
And I never got depressed because of renting.
I will rent debt free until I am dead
Spot-on analogy.
The thing that frustrates me about developers who feel powerless over technical debt is...who is actually stopping them from dealing with it? They way I see it, as a software engineer, your customer is sales/marketing/product/etc. They don't care about the details or maintenance, they just want the thing. And that's okay. But you have to include the cost of managing technical debt into the line items the customer wants. That is, estimate based on doing the right things, not taking shortcuts. Your customer isn't reading your commits. If they were, they wouldn't need you.
It would be bizarre if your quote for getting your house siding redone included line items for changing the oil on the work truck, organizing the shop, or training new crew members. But those costs of business are already factored into what you pay at the end of the day.
who is actually stopping them from dealing with it?
Management. Someone in management sets idiotic deadlines, then someone tells you “do X”, you estimate and come up with “it will take T amount of time” and production simply tells you “that’s too long, do it faster”
they don’t care about the details or maintenance
They don’t, they care about time. If there are 6 weeks to implement a feature that requires reworking half the product, they don’t care to know half the product needs to be reworked. They only care to hear you say that you’ll get it done in 6 weeks. And if you say that’s impossible, they tell you to do it anyway
you have to include the cost of managing technical debt
I do, and when I get asked why my time estimations are so long compared to those of other colleagues I say I include known costs that are required to develop the feature, as well as a buffer for known unknowns and unknown unknowns which, historically, has been necessary 100% of the time and never included causing us development difficulties and us running over cost and over time causing delays and quality issues that caused internal unhappiness, sometimes mandatory overtime, and usually a crappy product that the customers are unhappy with. That’s me doing a good job right? Except I got told to ignore all of that and only include the minimum time to get all of the dozens of tiny pieces working. We went over time, over cost, and each tiny piece “works” when taken in isolation but doesn’t really mix with everything else because there was no integration time and so each feature kinda just exists there on its own.
Then we do retrospectives in which we highlight all the process mistakes that we ran into only to do them all again next time. And I get blamed come performance review time because I was stressed and I wasn’t at the top of my game in the last year due to being chronically overburdened, overworked, and underpaid.
Yeah management is totally backwards there; it's like the building manager on a construction project going "all electrical needs to be done in X weeks", but realistically they have no direct control over that deadline being met by declaring an arbitrary deadline. The unfortunate difference is that if you do a shitty job wiring a building, you'll fail inspection and have to spend more time and money fixing it. Software can often hobble along; there aren't strict enforcements for quality that the business can legally ignore, so you'll always have sad defeated devs go "okay boss, we'll skip the things we need to get this done faster for you (I hate this job and don't care about the product's long term success)". Having a steady supply of those people will slowly kill a software company.
In the past, I've dealt with estimate pushback not by explaining what necessary work can be removed like tests, documentation, or refactoring, but by talking through ways to divide the project more effectively to get more people involved (up to a point, a la mythical man month). That seems to go more proactively. Then we look at nixing optional requirements. But, I've also usually dealt with mostly competent engineering management.
Yes, this. Refactor first to make the upcoming change easier and cleaner, not after. Don’t ask for permission, don’t even call it refactoring or cleanup. Just call it working on the feature, because that’s what it is. Don’t let non-engineers tell you how to engineer.
I believe for many companies, developers work on giant codebases with many hundred thousands or even millions of lines of code.
With such large codebase you have no control over any system. Because control is split between groups of devs.
If you want to refactor a single subsystem it would take coordination of all groups working on that part and will halt development, probably for months. But first you have to convince all the management people, that refactor is needed, that on itself could take eternity.
So instead you patch it on your end and call it a day.
So instead you patch it on your end and call it a day.
Yep!
I'm looking forward to the horror stories that emerge once some percentage of those changes are made solely by unmanaged hallucination-prone AI.
I would feel bad for the developera who have to clean up the mess, but honestly, it's their chance to make $$$$$$ off of that cleanup. If they manage not to, their union is completely incompetent.