Let's get the headline numbers out of the way. According to JetBrains AI Pulse 2026, 85% of developers now use or plan to use AI coding tools. Stack Overflow's 2025 developer survey puts that figure at 84%. Menlo Ventures found 51% use AI coding assistants daily — climbing to 65% at top-quartile organizations. These are not marginal numbers. This is near-total market penetration in under three years.

Now the other number. According to Value Add VC's synthesis of METR, McKinsey, and GitHub data released this month, trust in AI coding output has fallen from 40% in 2024 to 29% in 2026. More developers are using these tools every month. Fewer believe they're getting accurate results.

That's not a contradiction. It's a gap worth understanding.

The Productivity Number Nobody Agrees On

The hardest question in AI-assisted development is also the simplest: how much faster do AI tools make developers? The answer depends entirely on who you ask and how they measured it.

A widely cited SSRN paper (ID 4945566, n=4,867) found an MIT-anchored productivity gain of 26.08%. McKinsey's 2025 research put the figure higher for well-implemented workflows. GitHub's internal data has historically trended optimistic. Independent replication? Thin.

The discrepancy matters because companies are making billion-dollar infrastructure decisions based on numbers that don't always survive scrutiny. MIT's researchers measured a specific task type with specific tools. McKinsey's sample skews toward large enterprises with mature engineering cultures. Neither is wrong — but neither is generalizable.

What the data does consistently show: AI tools massively accelerate boilerplate and first-draft code. They provide moderate gains on well-specified, bounded problems. They provide minimal gains — sometimes negative — on ambiguous, architecturally complex work where context is everything.

That's not a knock on the tools. It's a description of where they actually live in the stack.

The Trust Deficit Has a Cause

So why is trust declining while adoption grows? Two reasons.

First, the novelty effect is gone. In 2023 and early 2024, developers were experimenting with AI completions and being wowed by the speed of autocomplete. The wow factor fades. What's left is a more honest reckoning with the quality of outputs — and developers, who are paid to care about correctness, are returning to the same conclusion: AI-generated code requires the same rigorous review as code written by a junior dev who doesn't fully understand the system.

Second, context windows are still the bottleneck. The more complex the task, the more context required to generate useful output. Shipping an AI coding assistant into a 500,000-line monorepo is a different problem than explaining a 200-line function. The tools are getting better at this, but "better" is not the same as "solved."

The Stack Overflow data is instructive: 46% of developers actively distrust AI accuracy. Not "have concerns." Don't trust it. In a field where a single production bug can cost millions, that's not a minor sentiment. That's a workflow constraint.

Where It's Actually Working

The 65% daily usage figure at top-quartile organizations hints at the real differentiator: workflow integration. Teams that have figured out where AI assistance adds consistent value — test generation, boilerplate scaffolding, documentation, code review first passes — are getting real returns. The gains compound when AI handles the repetitive work that burns out developers.

Agentic AI is where the gap is widening fastest. NVIDIA's 2026 State of AI survey found 48% of telecom companies deploying agents for multi-step workflows. That's not autocomplete — that's autonomous execution of bounded tasks. The productivity ceiling there is much higher than code completion, and the risk profile is different too.

Inference costs are falling fast. Epoch AI measured median LLM inference price drops of 200x per year since January 2024. At that rate, the economics that make AI-assisted workflows expensive today look very different in 24 months. The constraint won't be cost — it will be what you can reliably specify.

The Junior Developer Problem

One number that deserves more attention: employment of software developers aged 22–25 has fallen nearly 20% since 2024. That's a proxy for entry-level roles being compressed by AI tooling. When AI can handle the scaffolding and boilerplate that used to be a junior developer's primary job, the traditional onramp to senior work is disrupted.

This isn't a story about AI replacing developers. It's a story about AI replacing the path developers take to become senior. That's harder to solve, and it has consequences for team structure, hiring, and knowledge transfer that most companies haven't worked through yet.

The Bottom Line

AI coding tools are not overhyped in terms of adoption. They may be overhyped in terms of how far along the maturity curve they actually are. The 29% trust figure is a signal, not noise — and it's coming from the people who know the tools best.

The developers who are winning with AI tools are the ones who stopped asking "can AI do this?" and started asking "what exactly is this task, and does AI reliably do that part?" Specificity is the unlock. Vague enthusiasm is not.