State of Devs 2026

2026.stateofdevs.com

234 points by sgdesign 21 hours ago


adverbly - 7 hours ago

There needs to be a "what stage of grief are you in" question.

• Denial

• Anger

• Bargaining

• Depression

• Acceptance

Here is what I see(and common thought patterns)

• Denial (models will never be able to replace the majority of important work)

• Anger (angry at data centers, energy use, IP theft)

• Bargaining (people thinking that their personalized agentic dev setup or self-hosting is gonna somehow leave them with meaningful work long-term)

• Depression (people who are being honest about what it will mean to day-to-day lives of many workers in the industry over the next decade)

• Acceptance (people who are focused on the problems that get worse as AI gets better - social disruption, x-risk, government/corporate control)

sandeepkd - 18 hours ago

My hunch is that in the long run its going to be net negative in software. A lot of companies exists as of today cause a lot of people were able to just focus on building without constantly worrying about the fear of lay off. With the concept of job security based on talent and effort being dismantled, everyone would always be in a constant look out mode now.

beardbandit - 17 hours ago

> Within the next 5 years, how likely do you think it is that you will have to change careers due to reasons beyond your control?

When I filled this out myself in July, I was "somewhat unlikely"

If you ask me again now, only a few months later, I'm probably leaning towards "Somewhat likely".

Insane how fast this space is moving.

onion2k - 14 hours ago

Which of these workplace issues have you experienced throughout your professional career?

Bad Management: 63%

I don't think you can really ask whether people have seen 'bad management' without explaining exactly what that means. People, including me when I was a developer, often see 'bad management' as 'I don't agree with what I'm being told to do'. That's not necessarily bad management; far more often it's poor communication of the facts (although you could argue that's the bad management bit I guess.)

The things I used to think were bad management included hard deadlines, short term benefit projects that took on tech debt, not 'motivating' people by giving better raises, refusing promotions even though I thought someone was great, prioritising things that I didn't see the value in, etc. Those things maybe weren't bad management at all. I just didn't have the full facts.

This is the problem with surveys like this. Someone didn't get the raise they wanted, so they check the 'bad management' box for that tiny cathartic dopamine hit. It doesn't necessarily mean they've been badly managed.

serbuvlad - 9 hours ago

Let's be honest about it: this has been a long time coming. If you think of it in terms of the wider civilization, way too much human captial was tied up in software dev.

And the jobs therin are mostly very mundane and of a liniar-translation nature. (translate this Adobe XD design in CSS/React; translate these REST calls to SQL). And 80% of the time was spent chasing trivial mistakes.

Humans can do more for civilization than arranging react components.

benoau - 20 hours ago

Lot of very sad data but a couple of bright points:

- 50% are thinking somewhat-to-very unlikely they'll be changing careers in the next 5 years

- 42% are hopeful or excited about the tech industry

smackeyacky - 15 hours ago

At the start of the year when AI started being useful I really did experience a productivity gain. Having just started a new job, Claude was instrumental into quickly getting me going on an unfamiliar code base.

Now? I’m swamped with the dumbest jira tickets in history created by lazy AF project managers and business analysts who are using AI to create a pile of unmanageable slop while looking like superstars as they blithely point to their neatly arranged tickets.

I guess I could try to cope by pointing the AI back at it but for the first time I’m forced to color outside the lines just so I can deliver. None of it lines up with their garbage and so we’re now playing a stupid game of “let’s not and say we did” while I tick of useless tickets that shouldn’t even be in the project.

It is exhausting. Not due to the potentially increased velocity but due to the towering pile of slop getting shovelled over that needs fake responses. I don’t know what to do about that.

testerius - 13 hours ago

I do not get it. I know that there are different people but... Do you really have that many issues, problems with using AI for coding and solving problems in your jobs or hobbies? In my company using Codex and Claude help us a lot with our software. We were able to fix legacy software which we could not do earlier without AI because of current tasks going on. We migrated in 2 weeks* (read below) to new versions of framework and libraries. If we have to do it without AI, then it will be work for few months or even year - only if doing that work, not other work such as fixing bugs, maintaing systems and doing current work such as new features. In our case AI tools help us a lot - every single developer.

Notice: first working prototype was done after approximately 2 weeks and was done by one developer. Of course it had bugs and was not perfect but it was huge improvement compared to what was before. Imagine that you do not regularly update framework/libraries (as it should be) because of various reasons (client does not want to pay for it or you focus on different things). We understand our decisions and so on, we know it but real life sometimes can not be perfect. Thanks to Codex/Claude we can move forward. Of course we know the LLMs/AI tools are not perfect and magic problem solvers but we could not say that these tools make our lifes worse or something.

woah - 20 hours ago

Wonder what the selection bias is like on something like this