From Effective Code Reviews Without the Pain By Robert Bogue

Code reviews in most organizations are a painful experience for everyone involved. The developer often feels like it's a bashing session designed to beat out their will. The development leads are often confused as to what is important to point out and what isn't. And other developers that may be involved often use this as a chance to show how much better they can be by pointing out possible issues in someone else's code.

Code reviews, however, don't have to be painful.

Links to articles about code review:

• Wikipedia

• SmartBear software links from the wikipedia page (I'd bet the company put them up there.

  Best Kept Secrets of Peer Code Review (free book, some content available on line).

  Best Practices for Peer Code Review (a white paper from the same company.

• Macadamian's Code Review Checklist

• Frequently Asked Questions about mozilla.org's Code Review Process (not the usual code review by the team).