本文共 1173 字，大约阅读时间需要 3 分钟。

Regardless of which type of lightweight code review your team chooses, developers can apply proven techniques that prevent wasted time and improve results. 1. Limit the time dedicated for code review Spend no more than 60 to 90 minutes performing code reviews. 2. Go slowly To ensure an effective review, do not review more than 200 to 500 lines of code per hour. 3. Limit the amount of code reviewed Try to limit the total amount of code for a review to 200 to 400 lines. 4. Annotate the materials before the review starts By looking at code using tools other than their standard editors, developers can often spot problems in their own code before the review begins. 5. Keep Review checklists short If your team relies on checklists, make sure that they don’t include items that are obvious or can be detected via automation. Instead make sure that they focus on things that are easy to forget (e.g. “Are all errors handled correctly every where?”). Best practices are valuable in that they help users deliver repeatable process that they can tie to a ballpark prediction of results. The next point of consideration is the timing of code reviews in the Agile environment.

转载地址：http://oovdi.baihongyu.com/