AI
Code Review Becomes the New Bottleneck as AI Coding Tools Outpace Governance
GitLab's AI Accountability Report reveals a growing governance gap: developers now face the burden of validating AI-generated code they don't fully understand, while most organizations lack visibility into how agents operate across the software lifecycle.
The New Stack
The narrative around AI-assisted coding has shifted from speed to control. GitLab's new AI Accountability Report surveyed 1,528 developers and technology buyers across six countries, revealing a critical tension: while 78% of organizations report faster code commits with AI tools, 43% cannot reliably distinguish AI-generated code from human-written code in their own repositories.
Where the bottleneck moved#
"AI has shifted the bottleneck from writing code to reviewing it — 85% of our survey respondents confirmed this," according to Manav Khurana, GitLab's chief product and marketing officer. The problem is acute: developers now validate code they didn't write and may not fully understand, while review cycles stretch days-long.
The issue isn't unique to code speed. The full software development lifecycle—requirements, review, security, testing, deployment, maintenance—hasn't scaled to match AI's generation rate. Only 28% of organizations report their SDLC tools are fully integrated with shared data and workflows, creating blind spots where developers can't see security findings, policy governance, or risk resolution tied to agent-generated merge requests.
GitLab's infrastructure approach#
GitLab is addressing this with three technical pillars: a new Git backend for machine-scale agent execution (claiming 50x faster wall clock time and 1000x less network traffic in testing), a context graph called GitLab Orbit (showing up to 11x faster agent work and 45x fewer hallucinations), and governance automation that surfaces policy compliance directly in code review flows.
The core challenge GitLab identifies comes down to three questions most organizations can't answer about any line of AI code:
- Where did this code come from?
- What was it meant to do?
- Who is responsible for it in production?
The maturation of AI in engineering#
Khurana suggests the industry is entering a new phase focused on governance over raw generation speed. The data supports this shift: 91% of surveyed organizations plan to invest in AI code governance tools within 12 months, and 85% agree the next phase of AI in software will emphasize governance over generation.
For junior developers entering the field, the implications are significant. "One of the skills that matters most now is judgment," Khurana says. Understanding systems deeply and tracing code through pipelines, security findings, and production signals matters more than syntax knowledge alone.

