“We needed to slow down some of the migration work to avoid overwhelming the teams that had to do the reviews”
Quote · arxiv.org
From “How is Google using AI for internal code migrations?”, found 2026-10-14.
In the JUnit3 to JUnit4 migration (5,359 files in three months), Google deliberately capped how many changes it generated each week, because reviewers, not generation, set the pace.