Authored on: Feb 04, 2013
It's common sense that peer code review - in which software developers review each other's code before releasing software to QA - identifies bugs, encourages collaboration, and keeps code more maintainable.
But it's also clear that some code review techniques are inefficient and ineffective. The meetings often mandated by the review process take time and kill excitement. Strict process can stifle productivity, but lax process means no one knows whether reviews are effective or even happening. And the social ramifications of personal critique can ruin morale.
This 11 Best Practices for Peer Code Review describes 11 best practices for efficient, lightweight peer code review that have been proven to be effective by scientific study and by SmartBear's extensive field experience. Use these techniques to ensure your code reviews improve your code - without wasting your developers' time.