Our large database development team performs peer code reviews using a code review tool (http://smartbear.com/products/development-tools/code-review/). When we first started the process, it surprised me that some developers took defects and constructive suggestions for improvement as a personal attack on their competency. Most, however, understood the purpose of the review was to ensure adherence to standards and improve quality rather than public humiliation. It has taken some time but most developers have now learned the art of teamwork in reviewing code. Each developer is an individual who needs to be treated with respect and sensitivity with regards to their unique personality and how they take constructive criticism.

Not coincidently, the best developers tend to be the ones that embrace suggestions for improvement within project time constraints instead of trying to justify flawed code.