Two things I have found helpful: 1. Review collaboratively. If you have questions, ask other reviewers and the developers. By asking questions you aren't qu

Two things I have found helpful: 1. Review collaboratively. If you have questions, ask other reviewers and the developers. By asking questions you aren't questioning their wisdom, just pointing out that you don't understand what they wrote, so be respectful. 2. Introduce new programmers to the process gradually and require more collaboration than you would for more senior programmers. This helps ensure that new people are brought up to speed with appropriate mentoring from their senior staff. Review is a form of collaboration. It is a way to shake out logic before stuff gets into formal testing. Discussion is good.