1. Human code review remains valued and hard to abandon
Many commenters argue that senior engineers resist giving up line‑by‑line review, seeing it as essential for quality and knowledge transfer.
“We've had discussions about leaning more on automated review, but it hasn't translated into any practical improvements so far. I think senior engineers find it very difficult to give up on line‑by‑line review, no matter how much better the agents have gotten.” – staminade
2. AI‑accelerated coding shifts the bottleneck to review, testing, and analysis
While agents produce code faster, the process now stalls on reviewing that code, writing useful tests, or clarifying requirements.
“Code review was always a significant bottleneck and is even more so with agentic coding.” – staminade
“the baseline mean lines of code per month was 5017, the estimated increase was 1494 lines per worker‑month … the baseline mean for code review is 7.03 days” – hyperpape
3. Teams are exploring hybrid or spec‑driven processes to manage AI‑generated output
Instead of full manual review, participants suggest focusing human effort on high‑impact changes, defining clear quality bars, and codifying rules so agents can handle routine checks.
“Leave human review for the most impactful changes * Get better at defining the quality bar * Continually codify human concerns into rules or systems that can be checked against” – keybrd-intrrpt
“I think humans need to review requirements, specifications, and test scenarios.” – svachalek