Engineering teams across Asia are facing a new kind of gridlock. For years, the hold-up was writing code. Now, with AI churning out lines faster than any human can, the real logjam has shifted to the review process.
That is the central claim from Qodo, which this week rolled out version 2.8 of its AI code review platform. The update tackles a problem that is quietly eating developer time: code review itself.
Qodo CEO Itamar Friedman stated plainly that the bottleneck in DevOps has moved from writing code to reviewing it. Human developers, he argued, can no longer keep pace with the volume of code being generated. The numbers back that up.
As AI coding tools proliferate, more code is produced. Someone has to check it.
That someone is still a person. What Qodo is selling is a way to automate parts of that review. The new version includes a custom rules miner.
It scans existing codebase behavior and pull request history to find patterns. Those patterns become structured, enforceable rules. For a team in Manila or Singapore, the pitch is simple: less time arguing over whether to use tabs or spaces, more time actually shipping software.
There is also a new ability to discover AI skills across multiple repositories. These skills contain code review instructions, coding standards, and engineering best practices.
They surface in a central portal. DevOps teams can manage them there and assess their impact on software engineering workflows. For teams spread across Jakarta, this centralization could mean fewer late-night emergencies when a build breaks.
The underlying technology is graph-based. It tracks relationships between pieces of code.
When a developer submits a pull request that modifies a shared dependency, the agent reads all affected repositories. It surfaces impact findings before the pull request is merged. That means catching issues like function signature violations, contract breaks between APIs, changes to schemas, and infrastructure drift.
All of this happens before the code goes live. The stakes here are concrete. In a region where engineering teams are often lean and expectations are high, a broken build can cascade.
A single API contract break can stall an entire deployment pipeline. Developers in Manila or Singapore spend hours hunting down the source of a failure that could have been caught earlier.
Qodo is betting that teams will pay to avoid that friction. Friedman described these capabilities as extending an agentic AI platform for governing code. The language is careful.
This is not a tool for generating code. It is a tool for managing the consequences of code generation.
As AI writes more, the old review processes break. Human reviewers cannot scale linearly with machine output. Something has to give.
For now, Qodo is offering a structured answer. Whether teams adopt it depends on whether they feel the pain of the review bottleneck. In fast-moving DevOps shops, that pain is real.
The question is whether a platform can relieve it without creating new complexity. That remains to be seen.
{“@context”: “https://schema.org”, “@type”: “NewsArticle”, “headline”: “Qodo CEO Says AI Code Output Shifted DevOps Bottleneck to Review Stage”, “description”: “Engineering teams across Asia are facing a new kind of gridlock. For years, the hold-up was writing code. Now, with AI churning out lines faster…”, “datePublished”: “2026-06-25T18:52:00+00:00T09:30:00+00:00”, “author”: {“@type”: “Person”, “name”: “James Roberto”}, “publisher”: {“@type”: “Organization”, “name”: “InfoPulse Today”, “url”: “https://newsfeed.2bme.xyz/”}}
