3100 Opinions on Code Review in an AI World: Building Causal Theory from Practitioner Discourse
Summary
This study analyzes 3100 practitioner opinions on code review in an AI-driven development environment, addressing sharp disagreements about its evolving role. An initial observational analysis of public GitHub activity revealed that agent-authored pull requests are reviewed less often, merged several times faster, and discussed less than human-authored ones, though these trends proved unstable under different analysis choices. To uncover underlying mechanisms, researchers synthesized 38,709 grey-literature documents, including engineering blogs and Reddit threads. They then coded a stratified random sample of 3,100 documents using an LLM-assisted pipeline to construct a causal model. This model comprises 26 constructs and 67 relationships (64 directed, 3 contested). The central finding is that code review serves as the critical control point determining a coding agent's impact on software quality, with the team's human expertise and structured review process dictating the ultimate effect. The research also contributes a scalable, LLM-assisted method for building theory from grey literature.
Key takeaway
For software engineering managers integrating AI coding agents, recognize that AI's impact on software quality is not predetermined. Your team's human expertise and the structure of your code review process are the decisive factors. Prioritize investing in robust review protocols and continuous upskilling for human reviewers to ensure AI-authored pull requests maintain quality and foster understanding, rather than becoming a bottleneck or eroding knowledge.
Key insights
Code review is the control point for AI's impact on software quality, determined by human expertise and process.
Principles
- AI's effect on software quality is not fixed.
- Human expertise is crucial in AI-assisted review.
- Review process structure dictates AI's impact.
Method
Synthesize 38,709 grey-literature documents, filter for code review, code 3,100 with an LLM-assisted pipeline, then build a causal model of constructs and relationships.
In practice
- Use LLM-assisted pipelines for theory building.
- Analyze grey literature for practitioner discourse.
- Develop causal models from qualitative data.
Topics
- Code Review
- AI Coding Agents
- Software Engineering
- Causal Theory
- Grey Literature Analysis
- LLM-assisted Research
Best for: AI Scientist, Research Scientist, Software Engineer
Related on AIssential
See Counsel's argued verdicts on the open AI decisions leaders are weighing →
Editorial summary, takeaway, and curation by AIssential. Original article published by Artificial Intelligence.