Merge Branches Sooner with Synchronous Code Review
<p>Code review has the potential to be one of the most impactful activities we do in our day. It ensures our codebase remains readable and maintainable, catches bugs, spreads knowledge across the team, and increases our confidence in what we are about to release.</p>
<p>However, poorly structured code review processes can actively harm the team and their work. When the turnaround time of a code review stretches into days, code review chokes the flow of work through the team. We still gain the benefits of review, but each review blocks follow-on work, and the team finds itself pulling in additional streams of work while they wait for the review to complete.</p>
<p>Slow reviews create a negative feedback loop, where attempts to reduce the overhead of code review increase the size of each branch. Bigger, longer branches mean more difficult code reviews that take longer to complete. <a href="https://medium.com/swlh/3-problems-to-stop-looking-for-in-code-reviews-981bb169ba8b" rel="noopener">Feedback is delayed and comes after the developer has done enough work that pivoting is hard.</a> The team takes on a lot of additional cognitive load, tracking many large, different features simultaneously.</p>
<p><a href="https://steven-lemon182.medium.com/merge-branches-sooner-with-synchronous-code-review-78aa3cfb1df6">Click Here</a></p>