- Review your own code first.
- Write a clear change list description.
- Automate the easy stuff.
- Answer questions with the code itself.
- Narrowly scope changes.
- Separate functional and non-functional changes.
- Break up large change lists.
- Respond graciously to critiques.
- Be patient when your reviewer is wrong.
- Communicate your responses explicitly.
- Artfully solicit missing information.
- Award all ties to your reviewer.
- Minimize lag between rounds of review.
Source: John Crickett