InfoQ HomepageNewsAI Tools Accelerates Coding, but Not Overall Software Delivery, GitLab Research Finds
DevOps
Engineering for the Agentic Era: How to Spec, Build, Test, and Operate AI-Powered Systems (Webinar Jul 16th)
GitLab’s 2026 AI Accountability Report highlights an AI Paradox: although 78% of developers say they code faster, overall software delivery has not accelerated due to downstream testing and review bottlenecks and new challenges for enterprise governance and traceability.
According to GitLab research, AI has made the task of writing software faster, with 78% of respondents reporting faster code output and 73% noting that overall code quality has improved. However, AI tools have uncovered a deeper issue: organizations cannot easily control what they are shipping, as governance, traceability, and accountability have failed to keep pace, creating a structural imbalance.
The report defines AI accountability as the organizational and technical capability to answer three questions about any line of AI-generated code: where did it come from, what was it meant to do, and who is responsible for it once it’s in production? Most organizations cannot answer those questions today.
Indeed, 85% of respondents “agree AI has shifted the bottleneck from writing code to reviewing and validating it”. As a result, 79% report that overall software delivery process has not accelerated at the same pace as coding.
As Manav Khurana, Chief Product and Marketing Officer at GitLab, notes, recent events such as supply chain attacks, reliability issues, and regulators expectations, show that traceability is a critical concern to prevent organizational exposure. Respondents point to three main factors compounding into making traceability harder: difficulty distinguishing AI-generated from human-written code (43%), fragmented toolchains (40%), and systems that don’t track code origin (39%). Reflecting this gap, GitLab’s report observes that while:
87% are confident their team could determine within 24 hours whether AI-generated code contributed to a production incident, [only] 34% of organizations that experienced an incident in the past year could not actually make that determination.
For 85% of respondents, the solution lies in stronger governance, i.e. establishing clear policies to ensure provenance and accountability of AI-generated code. Without it, 83% of organizations view the accumulation of AI-generated code a risk, with 44% ranking it among their top technological concerns.
The findings in GitLab’s research echoes sentiments from an earlier Reddit thread, where the OP notes that continued investment into AI increased “speed at the text editor/terminal layer”, but left them spending most of their time “wading through the quicksand of agile/jira and middle management bloat”. Another user, YourMatt similarly noted that while the gains in coding speed were impressive, they did little to address the broader inefficiencies that ultimately constrain delivery:
sprint after sprint though, nobody in our focus group was churning out more story points than before. It really made it apparent how the mechanics of coding is a relatively small portion of our jobs.
In a more recent thread, Mestyo reinforces this view, arguing that the majority of work performed by individual contributors cannot be meaningfully accelerated by AI coding tools.
As a final note from the community, Reddit user EveryDay_is_LegDay echoes this perspective, arguing from experience that testing remains the primary bottleneck and that “producing code faster only exacerbates the problems of most development teams”.
