What are the key takeaways from this Software Engineering Daily episode?

Key insights include: **The Verification Gap:** 42% of developer code is currently AI-generated, projected to reach 65% by 2027, yet 96% of developers do not fully trust AI-produced code. Engineering leaders must implement deterministic verification layers — tools that produce consistent, low-false-positive results — before shipping AI-generated code into production environments.; **The Great Toil Shift:** AI eliminates traditional toil tasks like writing documentation and tests, but replaces them with new toil: reviewing and verifying AI-generated code. Developers using AI daily spend roughly the same total time on toil as those who do not, and 38% report that reviewing AI code is harder than reviewing human-written code.; **Shadow AI Risk:** 35% of developers access AI tools through personal accounts rather than corporate-sanctioned platforms, exposing organizational IP and data to ungoverned third-party systems. Engineering leaders should establish governance policies that account for agentic workflows, where multiple agents exchange code, prompts, and context data simultaneously.

What did Chris Grams and Manesh Kapoor discuss on Software Engineering Daily?

Sonar's Chris Grams and Manish Kapoor discuss their State of Code Developer Survey with host Matt Merrill, revealing that 42% of developer code is already AI-generated, 96% of developers distrust that code, and how deterministic verification layers like SonarQube address the resulting quality and security gap. Key topics include: **The Verification Gap:** 42% of developer code is currently AI-generated, projected to reach 65% by 2027, yet 96% of developers do not fully trust AI-produced code. Engineering leaders must implement deterministic verification layers — tools that produce consistent, low-false-positive results — before shipping AI-generated code into production environments.; **The Great Toil Shift:** AI eliminates traditional toil tasks like writing documentation and tests, but replaces them with new toil: reviewing and verifying AI-generated code. Developers using AI daily spend roughly the same total time on toil as those who do not, and 38% report that reviewing AI code is harder than reviewing human-written code..

How long is this episode of Software Engineering Daily?

This episode is 59 minutes long. SignalCast provides an AI-generated summary so you can get the key insights in about 3 minutes.

Software Engineering Daily

Hype and Reality of the AI Coding Shift

April 23, 2026

59 min episode · 2 min read

Chris Grams,Manesh Kapoor

Episode

59 min

Read time

2 min

Topics

Productivity, Investing, Fundraising & VC

AI-Generated Summary

Published Apr 23, 2026

Key Takeaways

✓The Verification Gap: 42% of developer code is currently AI-generated, projected to reach 65% by 2027, yet 96% of developers do not fully trust AI-produced code. Engineering leaders must implement deterministic verification layers — tools that produce consistent, low-false-positive results — before shipping AI-generated code into production environments.
✓The Great Toil Shift: AI eliminates traditional toil tasks like writing documentation and tests, but replaces them with new toil: reviewing and verifying AI-generated code. Developers using AI daily spend roughly the same total time on toil as those who do not, and 38% report that reviewing AI code is harder than reviewing human-written code.
✓Shadow AI Risk: 35% of developers access AI tools through personal accounts rather than corporate-sanctioned platforms, exposing organizational IP and data to ungoverned third-party systems. Engineering leaders should establish governance policies that account for agentic workflows, where multiple agents exchange code, prompts, and context data simultaneously.
✓LLM Selection Beyond Benchmarks: Standard coding benchmarks only measure functional correctness. Sonar's leaderboard at sonar.com/leaderboard evaluates 35 models across security vulnerabilities, bug density, cognitive complexity, and cyclomatic complexity per million lines of code. Higher-performing models often produce more verbose, complex code — making holistic evaluation across all dimensions necessary before selecting a model for production use.
✓Experience-Based AI Usage Divergence: Junior developers report 40% productivity gains from AI tools but 66% admit the generated code appears correct while being functionally broken. Senior developers predominantly use AI for understanding legacy code and writing documentation. Both groups benefit from maintaining existing robust code review processes, which apply equally to AI-generated and human-written code.

What It Covers

Sonar's Chris Grams and Manish Kapoor discuss their State of Code Developer Survey with host Matt Merrill, revealing that 42% of developer code is already AI-generated, 96% of developers distrust that code, and how deterministic verification layers like SonarQube address the resulting quality and security gap.

Key Questions Answered

•The Verification Gap: 42% of developer code is currently AI-generated, projected to reach 65% by 2027, yet 96% of developers do not fully trust AI-produced code. Engineering leaders must implement deterministic verification layers — tools that produce consistent, low-false-positive results — before shipping AI-generated code into production environments.
•The Great Toil Shift: AI eliminates traditional toil tasks like writing documentation and tests, but replaces them with new toil: reviewing and verifying AI-generated code. Developers using AI daily spend roughly the same total time on toil as those who do not, and 38% report that reviewing AI code is harder than reviewing human-written code.
•Shadow AI Risk: 35% of developers access AI tools through personal accounts rather than corporate-sanctioned platforms, exposing organizational IP and data to ungoverned third-party systems. Engineering leaders should establish governance policies that account for agentic workflows, where multiple agents exchange code, prompts, and context data simultaneously.
•LLM Selection Beyond Benchmarks: Standard coding benchmarks only measure functional correctness. Sonar's leaderboard at sonar.com/leaderboard evaluates 35 models across security vulnerabilities, bug density, cognitive complexity, and cyclomatic complexity per million lines of code. Higher-performing models often produce more verbose, complex code — making holistic evaluation across all dimensions necessary before selecting a model for production use.
•Experience-Based AI Usage Divergence: Junior developers report 40% productivity gains from AI tools but 66% admit the generated code appears correct while being functionally broken. Senior developers predominantly use AI for understanding legacy code and writing documentation. Both groups benefit from maintaining existing robust code review processes, which apply equally to AI-generated and human-written code.

Notable Moment

Sonar's analysis revealed that as LLM performance improved through most of 2024, code complexity scaled linearly alongside it — smarter models wrote more verbose, harder-to-maintain code. Only around November did top models begin producing performant code without the corresponding complexity increase, signaling a meaningful shift in model behavior.

Know someone who'd find this useful?

Episode Transcript

AI coding tools have gone from novelty to core infrastructure in under three years. Today, many devs use AI daily. A substantial share of new code is AI generated, and expectations for automation are rapidly increasing. Sonar is a company specializing in analysis of code quality and security, and they recently released a new survey, the State of Code Developer Survey. The survey provides a deep examination of how developers are using AI in real production environments and where the real world gaps and risks still exist. Chris Grams is the CVP of corporate marketing at Sonar, and Manesh Kapoor is the VP of product marketing and developer relations at Sonar. In this episode, they join Matt Merrill to discuss what the survey reveals about AI assisted development, why 96% of developers still don't fully trust AI generated code, how deterministic verification layers fit into agent driven workflows, and what engineering leaders should prioritize as AI shifts from experimentation to production infrastructure. Matt Merrill is a software engineering leader with over twenty years of experience building and scaling software teams across enterprise and product focused organizations. His background is in back end development, cloud architecture, and distributed systems design. He currently architects and delivers software products and leads a team of engineers at Dept Agency. You can learn more about his work at code. The other mattm.com. I am here with a couple of folks from Sonar to talk about the State of Code Developer Survey Report. So before we get started, Manish and Chris, would you guys mind introducing yourselves and talking about your background and what you do at Sonar? Manish, you wanna go first? Sure. Nice to meet you, Matt, and thanks for having us on the program. Chris Grams. I'm the VP of corporate marketing here at Sonar, which might immediately make people wanna stop listening, except for the fact that I would say I'm also sort of our resident data in survey nerd. So probably know the survey results coming out of this better than most. I've been in enterprise tech for a long time. I started out early in my career at Red Hat. I spent about a decade and then went on to work with a bunch of other software companies in the consulting role. And then was one of the early employees at Tidelift, which is a company that sponsors open source maintainers and was acquired by Sonar about a year ago. So I've been with Sonar in this role just over a year. Nice. Well, nice to meet you. Manish? Yeah. Nice to meet you. Hi, Matt. Nice to meet you. Thanks for having us here. I'm Manish. I'm based in Austin. I've been with Sonar for about two and a half years, almost three years now. Like Chris, I have got a long history with the enterprise software background. I started with Sun Microsystems, and then I joined Oracle, and here I am at Sonar. I've worn different hats in …

Get the full transcript (11,197 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Software Engineering Daily transcripts →

You just read a 3-minute summary of a 56-minute episode.

Get Software Engineering Daily summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links.

Tools

SonarQubeRecommended
by Sonar
“deterministic verification layers like SonarQube address the resulting quality and security gap”
Sonar LeaderboardRecommended
by Sonar
“Sonar's leaderboard at sonar.com/leaderboard evaluates 35 models across security vulnerabilities, bug density, cognitive complexity, and cyclomatic complexity per million lines of code”