Purpose of Code Reviews¶

1. It takes far less time to find bugs during a code review than to test and debug code.
2. The fact that a colleague will be viewing your code is a huge motivation for writing good code and bug free code from the start.
3. By walking another person through your code, you are no longer the only living human that understands what you were thinking! (Good for maintenance)
4. If there is a problem with your code, you share responsibility for the bug with the person who performed the review. (It's not ALL your fault.)
5. It is extremely difficult and prohibitively time consuming to test every decision path of a function. A code review may be the only quality assurance available.
6. Code reviews provide a valuable opportunity for sharing knowledge and exchanging coding techniques.