Key Takeaways

• Pull Request-based async code reviews are a prevailing way of reviewing code in our industry
• When feedback is invited only after making a lot of changes, it becomes very difficult for both the PR reviewer(s) and the author to course-correct and build in quality
• Delays are an inherent property of asynchronous reviews, and they increase PR batch transaction cost
• With small Pull Requests, we lose throughput if we review them asynchronously because delays in communication start dominating PR lead time
• Co-creation patterns, Pair and Mob Programming enable continuous code review which enables both high throughput and high quality