Article by Garrett Smith
Peer code review is where software developers review each others' development code.
The number one benefit to code reviews is code quality. Code reviews make the code better. Here are some other benefits:
Take your time understand the problem and how it is addressed in the solution.
Focus on a small piece at a time.
A code review should be objective and should state actual problems. Saying "the code is bad" is not a helpful review. Instead, explain the problem clearly. If the problem is severe, then say why.
This section is for the the reviewee (the person whose code is being reviewed).
The reviewee should prepare for a code review by following the the code guidelines.
When posting code to the newsgroup, it is important to make sure to transmit it such that it can be easily read and understood.
By focusing carefully on small sections, the code review can find more bugs. The reviewer may want to spend an hour reviewing the code, then come back to re-review his notes and comments for another hour.
The reveiwee may challenge a criticism and, if the challenge cannot be rebutted, the criticism shall be withdrawn.