DEV

Eighty-three percent of developers now use AI tools at work — yet only 6.6% fully trust the output. This episode unpacks the data behind that striking gap and what it reveals about how the profession is actually evolving.

Show Notes

Widespread AI adoption among software developers is no longer a trend to watch — it's the current reality. But a sweeping Stack Overflow survey of nearly 31,000 developers reveals a striking contradiction at the heart of that reality: near-universal tool usage paired with near-zero unconditional trust. This episode of DEV.co digs into the software development statistics behind the 83% adoption and 6.6% trust figures to explain what that gap actually means for engineering teams and the profession at large.

The episode covers a wide range of data points from the 2026 survey landscape and beyond, including:

  • The adoption-favorability flip: In 2023, optimism outpaced usage; by 2025–2026, the inverse became true — more developers use AI than feel genuinely good about it, signaling a more hard-nosed, experienced relationship with the tools.
  • How trust actually breaks down: The single largest group of developers — 48% — said they trust AI output only when they can easily verify it themselves; just 6.6% trust it completely, while 12.3% don't trust it at all.
  • Where AI earns its keep: Code generation in familiar domains (69%), debugging and refactoring (64%), and quick Q&A (59%) dominate use cases — all areas where developers can quickly judge whether the output is correct.
  • Where developers draw the line: Nearly 36% say they don't use AI for production systems and have no plans to — a posture the episode frames as rational risk management, not resistance to change.
  • The agent-driven pull request surge: GitHub data shows agent-started pull requests jumped from 17% to over 40% of all PRs between March and September 2026 — representing 110 million agent-initiated drafts in a single month, with human developers still deciding what ships.
  • Tool fragmentation over dominance: Claude Code leads at 65.5% usage, followed by GitHub Copilot at 58.7%, but 40% of developers use three to five distinct AI products weekly — the market remains pluralistic and experimental.
  • Job market outlook: U.S. Bureau of Labor Statistics data projects 10% developer job growth by 2035, more than three times the average for all occupations, with median salaries at roughly 2.7× the national median — not the picture of a profession being displaced.

The episode also contextualizes these findings for teams building AI-powered products — whether that means integrating AI into existing workflows or developing new custom AI applications where the same trust and verification questions arise in a production context.

For more on a related topic, don't miss the earlier episode Private RAG Over Microsoft 365: Permissions, Delta Queries, and What Actually Ships, which explores how retrieval-augmented generation is being deployed responsibly inside enterprise environments.

softwaredevelopmentservices.ai

RFP.co

What is DEV?

Software and web development from the side that has to ship it and then live with it. Architecture decisions with a cost attached, scoping, technical debt, hiring and vendor selection, and the AI tooling question every engineering team is now answering whether they planned to or not.

Each episode takes one decision — rewrite or refactor, framework choice, build versus buy, how to scope a fixed-bid project honestly — and works through the tradeoffs, including the ones that only show up in year two. Written for engineering leads, technical founders and the people who fund them. Five or six minutes, no hand-waving.

Topics include rewrite versus refactor, build versus buy, scoping fixed-bid work honestly, technical debt you should keep, framework and platform choices, hiring and vendor selection, code review culture, and where AI tooling actually helps.

Produced by DEV.co, web and software development. Full details, services and further reading at https://dev.co