Liz Fong-Jones: 2x the PRs, 1.5x the Incidents
The rapid adoption of AI coding agents (like those generating pull requests) is accelerating development volume (e.g., 30 to 70 PRs/day) but does not automatically solve systemic reliability issues. The core challenge is scaling human review capacity. The discussion emphasizes that AI amplifies existing organizational practices—magnifying both high ownership and dysfunction. To safely scale, organizations must focus on improving guardrails, implementing automated review classifiers (like Jev), enforcing strong CI/CD patterns, and ensuring human accountability remains paramount, especially during production incidents.
Key takeaways
-
AI amplifies existing organizational practices.
18:14
AI will not fix existing problems; it will magnify them. Organizations must first fix underlying issues (e.g., poor ownership, weak patterns) before introducing AI to accelerate the path.
-
Automated code review is critical for scaling review capacity.
23:21
Tools like Honeycomb's Autobot focus on automating the review process, allowing human developers to focus on complex design patterns rather than trivial bugs. The bottleneck shifts from code generation to code validation.
-
Using classifiers (like Jev) for PR safety.
35:30
A key strategy is classifying PRs into 'safe to merge automatically' versus 'requires human review.' This focuses human attention on the most complex or risky changes, rather than attempting to review every PR.
-
Ownership and accountability remain non-negotiable.
The principle 'If your name's on it, you own it' must extend beyond code to include the responsibility for hardening systems and analyzing failures. 'Claude did it' is not an acceptable excuse.
-
Production maturity dictates AI agent trust.
AI agents can only operate safely if the underlying system has mature practices, including working automatic rollbacks, feature flags, and robust observability. Without these, agents are 'throwing darts at the dartboard.'