# Google, McKinsey & Dave Farley on AI Code Review

## Executive summary

The rapid acceleration of AI code generation creates a critical bottleneck in traditional software development processes, specifically the code review phase. Speakers discuss how the current ratio—where generating code is fast (seconds) but reviewing it remains slow (hours)—is breaking down established social contracts and trust within open-source collaboration. Solutions proposed include shifting focus from quality control to engaging with mental models, implementing advanced agent memory systems (like Tapes), and prioritizing precise, prescriptive language over vague natural language.

## Key takeaways

- The Code Review Bottleneck: Current processes assume a slow ratio: generating code takes 30 seconds, but reviewing it can take an hour. This mismatch strains maintainers, especially when agents generate multiple pull requests (PRs) rapidly, leading to 'trust breakdown' regarding who actually reviewed the code.
- Reviewing Mental Models: Code review should not be viewed as quality control. Instead, it is a mechanism for engaging with and aligning multiple mental models (the developer’s model, the system’s model, and colleagues' models). Maladaptive creativity can cause these three models to diverge.
- Agent Hallucination & Memory: AI agents can 'politely hallucinate,' reporting progress without actual learning or completion. To combat this, advanced systems must capture raw agent sessions and process them into structured 'observational memory' for continuous improvement.
- Precision over Natural Language: Natural language is inherently vague and open to misinterpretation, making it insufficient as the sole programming language of the future. Precision requires prescriptive instructions that go beyond general conversational prompts.

## Technical details

- Agent Development & CLI Tools: Jack Wotherspoon works on Google ADK and Gemini CLI, focusing on how AI agents impact open-source contribution models (e.g., Antigravity CLI).
- Data Persistence for Agents: Brian Douglas uses a Tapes database (migrating from SQLite to Postgres) to store raw agent logs and process them into 'observational memory' records, allowing agents to learn from past sessions.
- Agent Parallelization: The difficulty in parallelizing human thought processes is contrasted with the ease of having multiple subagents running simultaneously, placing a massive review burden on maintainers.
- Language Precision: Dave Farley argues that natural language is too vague for programming. He advocates for using precise, prescriptive language to prompt agents effectively, even if the code itself isn't hand-written.

## Practical implications

- Re-evaluate code review processes to focus on mental model alignment rather than just bug detection.
- Implement robust logging and memory capture systems (like Tapes) to track agent behavior and prevent loss of context.
- Develop tooling that forces developers/agents to articulate the 'why' behind a change, addressing trust issues.
- Prioritize structured, prescriptive prompting techniques over vague natural language instructions for AI agents.

## Topics

AI Engineering, Code Review, Continuous Integration (CI), Agentic Workflows, Software Architecture, Google ADK, Gemini CLI, Tapes database, Postgres

Source: https://www.youtube.com/watch?v=fwL31sNbq8g