AI Coding's Real Bottleneck Isn't Code Review
Techstrong TV Interviews
•
17m
AI coding tools have made engineers faster, but they haven't made companies faster. Mike Vizard talks with Adir Ben-Yehuda, CEO and co-founder of AutonomyAI, about why more code review is the wrong fix and what teams should change instead.
Why more AI coding isn't faster software
Coding agents now generate more code than ever. However, much of it never reaches production. AutonomyAI recently spoke with more than 130 software organizations for its research report, The Bottleneck Moved. The common thread was clear. The bottleneck isn't only in reviewing code. Instead, it sits in the process of who gets to build what.
Change the process, not just the tools
Over the last 18 months, teams added coding agents, then harnesses, then more software around them. Now they're adding review tools. Ben-Yehuda says you can't keep stacking tool on tool without changing the process itself. Likewise, hiring more reviewers just puts more people on the same problem.
He suggests splitting the work into three parts: architecture, system stability and the application layer. Product managers and designers can then own the application layer. As a result, engineers are free to focus on architecture. At AutonomyAI, a PM can have a hypothesis on Monday and see it in production by Friday.
AI coding needs context and guardrails
Foundation models keep getting smarter. Still, Ben-Yehuda believes they need an application layer that supplies context for each organization. Teams also need clear roles and responsibilities for every AI agent. Otherwise, agents drift and conflict.
He also flags a new enablement problem. Features now ship faster than sales teams can learn them. One fix is to generate a short video for every merge and send it to account executives.
Where AI coding goes next
Looking ahead, Ben-Yehuda expects always-on agents that act on company metrics without waiting for a trigger. DevOps and platform engineers will build the guardrails that let anyone in the business create applications.
His advice is practical. First, treat AI as a learning system and give it at least two quarters. Then start with small tasks, such as helping PMs write better PRDs. Finally, measure the results and go deeper once trust is built.
Up Next in Techstrong TV Interviews
-
SentinelOne Brings Detection and Resp...
Employees now run AI agents on nearly every desktop, and most security teams can't see what those agents are doing. Alan Shimel talks with Chris Corde, chief product officer at SentinelOne, about agent detection and response and the ASOC news from OneCon 2026.
From Google Cloud security to S...
-
Tricentis on Why AI-Generated Code Ne...
Coding agents now write much of today's software, but they can't be trusted to test their own work. Alan Shimel talks with David Colwell, VP of AI and machine learning at Tricentis, about why AI-generated code needs agentic testing.
Building AI into Tricentis since 2018
Colwell spent year...
-
JoyStream.ai Builds an Operating Syst...
Most AI agents still live on someone's laptop, driven by prompts that can change at any time. Alan Shimel talks with Harpreet Singh, CEO of JoyStream.ai, and Vivek Pandey, its co-founder and CTO, about building an operating system for AI agents.
From Sun Microsystems to JoyStream
Singh an...