In the last post we covered a review process where the code review is performed after all the code is written with the goal of approving the suggested changes. If getting the design right is important to your team, then a collaborative and iterative approach may be appropriate — the code can be checked frequently while it's being built, so design feedback comes at the right time. In this example, I'm going to assume the team works using feature branches. As with anything, this approach has its supporters and detractors, but it's a reasonable model to showcase iterative code reviews. The