DiscussionTechnical

Humans are still the bottleneck in Warp’s AI factory

How I AI

Warp discusses how human code review has become the main bottleneck in their AI-assisted software development process, with a 3.5-hour delay from PR to first human review compared to 35 minutes from launch to PR. They're evolving their workflow to reduce human dependency by allowing requesters to review agent-generated code themselves, and plan to eventually skip review entirely for low-risk tasks by treating code review as a risk management exercise.

Summary

Warp's development team identifies a significant inefficiency in their AI-driven software development workflow. While their AI agent can produce code and create pull requests in just 35 minutes from launch, the process then stalls for 3.5 hours waiting for human review—making humans the primary bottleneck in their development cycle. The team previously followed a two-person review model where Person A would create code using an AI agent and Person B would review it. They've since evolved this workflow so that the person requesting the agent's work can review the generated code themselves, reducing coordination overhead. However, they acknowledge this still doesn't provide full confidence in the process. Looking forward, Warp expects their approach to mature further by gradually building confidence in skipping human code review for certain categories of tasks based on risk level. The team frames this evolution as a transition where code review transforms from a mandatory step into a strategic risk management exercise—selectively applied based on task complexity and risk profile rather than applied uniformly to all pull requests.

Key Insights

  • Warp's AI can produce code and create pull requests in 35 minutes, but humans take 3.5 hours to review—making human review the actual bottleneck despite AI acceleration elsewhere
  • Warp changed their workflow so the person requesting AI-generated code reviews it themselves rather than requiring a separate reviewer, eliminating coordination overhead
  • Despite workflow improvements, Warp still lacks full confidence in skipping human code review entirely for all tasks
  • Warp plans to gradually skip code review for certain percentages of tasks as confidence builds, rather than applying human review universally
  • Warp expects code review to evolve into a risk management exercise rather than a mandatory process applied to all pull requests

Topics

Human bottleneck in AI-assisted developmentCode review workflow optimizationAI-generated code validationRisk management in automated developmentDeveloper productivity and process efficiency

Transcript

[0:00] People are slowing down the software development process a bit . Can we have a little discussion about whether people are really a " bottleneck"? Because if you look at the time from launch to PR, it's 35 minutes. But if from PR to the first human view, it's 3.5 hours. And it's so funny that the cycle still takes so long, man. This is what is really worth focusing on. So it's on this number. They are still a " bottleneck". We still do human code review. Currently, all of our PRs undergo human code review. Previously, the workflow was like this: [0:30] Person A on our team creates something with an agent, and Person B reviews the…

Full transcript available for MurmurCast members

Sign Up to Access

More from How I AI

Get AI summaries like this delivered to your inbox daily

Get AI summaries delivered to your inbox

MurmurCast summarizes your YouTube channels, podcasts, and newsletters into one daily email digest.