You might have seen the State of JavaScript survey before, but did you know there's now a State of Web Dev AI survey as well?
I just published the...
For further actions, you may consider blocking this person and/or reporting abuse
I read that the public sentiment on AI is still on a nosedive. This is more apparent on new college graduates. Let's see how they handle it these coming years.
Hi! Elmar Chavez hope you are doing well. I am a beginner in this field, and I came across your profile. Since you have experience, I would be incredibly grateful if I could ask you a few questions or get some guidance from you whenever you have some free time. Looking forward to hearing from you. Thanks a lot!"❤️
Glad to hear that, you can message me thru LinkedIn 🙂
Bro, I don’t have a LinkedIn account because my dad doesn’t allow me to make one.😅
Can you explain the difference between block-level elements and inline elements in HTML with some examples? I’m trying to understand it better.
I suspect many of the "anti-AI" college graduates still use ChatGPT to help with assignments…
These numbers are truly astounding 😵 Especially the proportion of code generated by AI tools and potential threats give some food for thought. Call me naive, but I never considered military use of AI as a threat... I don't even want to think about how much damage AI could do in the wrong hands of some powerful officials 🫣
Seriously? It's already happening in Gaza and West Asia. Wrong officials already have access to AI enhanced weapons... Just Europe isn't the target (yet).
How exactly is AI used in these cases?
The data from the State of Web Dev AI survey really highlights the shift in developer sentiment. We've moved past the "AI will take my job" fear and straight into the practical concerns of unmaintainable, AI-generated technical debt. When it's easier to generate a new feature than to read the code running it, we have a serious maintainability crisis on our hands.
I find it a bit concerning how few people are seeing the angle that the ability to build software is moving from someone you can learn to something you have to buy. Maintainability concerns are valid, but the broader cultural effects are relevant on a much larger scale.
My AI fear is the pandemic of "Cognitive Atrophy" that is about to hit those whose job are not taken by AI but impacted by +50%. We could well see humans losing the ability to think for themselves let alone reason and problem solve.
For me as a software developer, I am concerned that AI (LLMs) will take the part of my job I find most rewarding, leaving me with the parts I hate. When than happens I will be looking for a career change.
They used to say, they don't pay software developers to code (but they will pay tech bros!) but to think. That is not quite true. They should be paying software developers to grain an understanding of the problem and formulate a compatible solution. I am not sure they can say that about the LLMs! Their only real skill is pattern matching.
The same problem is mirrored on the larger scale too: As the workforce gets used to AI solving most problems, it forgets how to build things from scratch. Junior developers no longer turn into senior developers, and eventually, too few people are left to generate new original code to train AI on and things get ugly.
I feel the same way. The implications of a society that cannot think for itself are dark. It makes us easier to manipulate and control.
The risk angle I'd add: vendor concentration. Most production LLM workloads in 2026 hit just 2-3 APIs (OpenAI, Anthropic, Google) — if any of them tightens pricing or terms mid-year, half the SaaS layer built on them collapses overnight. The mitigation isn't building local infrastructure (too expensive for most teams), it's keeping wire compatibility across providers so you can swap in a day, not a quarter. Underdiscussed compared to AGI doom takes.
If the AI bubble bursts, they'll all increase prices at the same time in an attempt to prove profitability. There's no way to mitigate that other than to simply be prepared to pay more or switch back to non-AI solutions where it's no longer profitable to use AI.
Fair point on the bubble scenario — if everyone hikes together, compatibility doesn't save you on absolute cost. The case for portability is more about non-price risk: sudden ToS changes, deprecations, geographic restrictions, and rate-limit policy moves which are per-vendor and don't track macro pricing. You can't escape the bubble, but you can escape any single vendor's bad decision.
curious what the survey split looks like between teams that have any written constraints on what agents can do vs teams running agents purely on vibes. that gap feels like the actual risk, not AI capability itself.
The jump to 54% of all code being AI-generated in the survey data is wild, but the psychological shift is the most concerning part.
Spot on. The most immediate risk of 2026 isn't evil AI; it’s a silent, compounding degradation of data integrity. When models train on synthetic data, and agents ingest unstructured, ambient web text, the signal-to-noise ratio plummets.
This is exactly why architectural patterns are shifting toward strict zero-trust data boundaries. If we aren't aggressively filtering and validating input footprints before they hit an execution runtime, we're just subsidizing the entropy. Thanks for highlighting the real battleground.
Excellent article, and thank you for sharing the survey. As an experienced developer, I use AI and always make sure to review the code it produces before committing it. We should embrace, align and engage with AI rather than overlook it and getting ignored.
Great point. The TypeScript generics section here is particularly important — I see so many codebases with overly complex type hierarchies that could be simplified.
A pattern that's saved me hours: when your generic constraints get too complex, step back and ask if you're modeling the right abstraction. Often the solution is splitting the type into smaller, focused pieces.
One thing I'd add: conditional types are more powerful than most people realize. A well-placed extends check can eliminate an entire class of runtime errors.
The risk that keeps me up isn't superintelligence — it's the boring operational stuff nobody talks about. We're wiring LLMs into CI pipelines, customer support routing, code review workflows, and every single integration has a silent failure mode baked in.
Example: an agent that summarizes bug reports before routing them to the right team. Works great 95% of the time. That 5% where it misclassifies a P0 as a P2? The summary looks plausible, nobody double-checks it, and the bug sits in a queue for 3 weeks. The failure is invisible because the agent output looks correct.
I think the 2026 risk isn't a Skynet scenario. It's thousands of these invisible cascading failures across interconnected systems, where no single component is obviously broken but the whole stack degrades in ways nobody can trace. Are you more worried about catastrophic failure modes or this kind of slow-motion entropy?
The jump from 28% to 54% AI-generated code in one year is striking. But the more interesting number is probably hidden in the variance — a senior dev using Claude Code for boilerplate might report 80%, while a junior leaning on it for logic they don't fully understand reports the same 80% with very different risk profiles. Would love to see next year's survey cross-reference AI code percentage with years of experience and production incident rates.
You can already do that with the query builder, and the result isn't all that interesting.
As far as I could tell, the only variable that consistently splits results is, surprisingly, gender.
One of the most concerning AI risks in 2026 is misinformation at scale. AI can create realistic text, images, and videos very quickly, which makes false information spread faster than ever. For businesses, this can impact customer trust, brand reputation, and even search visibility when misleading content starts ranking online.
Another major concern is overdependence on AI-generated content without human review. AI helps with speed, but accuracy, creativity, and brand voice still need real people behind them.
At AQVA Marketing, we see AI as a powerful tool for content, SEO, and digital growth—but the best results come when AI supports strategy while humans handle quality, trust, and meaningful customer connection.
One very interesting insight imho were the gender ratios in the replies.
Important framing, want to pivot from web-dev to voice. The real 2026 risk for our line is conversational agents that sound confident on PSTN with no transcript-level eval gate. We had an agent quote a customer the wrong refund policy with full confidence and zero hedging. Took 6 hours and one angry tweet to surface. Co-simulation is the only honest test: run the agent against a corpus of recorded real-world calls (with PII scrubbed) and grade the transcripts in batch, not just unit-test the LLM in isolation.
Interesting point.
I think the biggest AI risk in 2026 may not be “AI replacing developers.”
It may be developers becoming too confident in AI-generated output without fully understanding the system underneath.
AI coding tools are already extremely good at:
scaffolding
refactoring
generating boilerplate
speeding up repetitive work
But once projects become larger, problems start appearing:
hidden architectural mistakes
context drift
silent logic regressions
over-trusting generated code
After building several AI-assisted projects myself, I’ve noticed something:
AI increases development speed dramatically…
…but it can also increase the speed of technical debt if teams stop reviewing architecture carefully.
I think the future skill gap won’t simply be:
“Who can use AI?”
It’ll become:
“Who can still think critically while using AI?”
That’s probably where experienced engineers will continue to matter a lot.
The survey results are fascinating — 7000+ devs is a solid sample size. The "most concerning" finding matches what we're seeing in the agent space: the risk isn't job replacement, it's gradual skill erosion and over-reliance.
One data point I'd love to see broken out — how do the answers differ between devs who've deployed AI in production vs those who've only experimented? Our experience suggests the two groups have very different risk perceptions.
This was a nice and interesting read. Love pulling up stuff like this 🤩
Good post, thank you.