Purpose of Code Reviews » History » Version 1
Amber Herold, 03/04/2010 04:16 PM
| 1 | 1 | Amber Herold | h1. Purpose of Code Reviews |
|---|---|---|---|
| 2 | |||
| 3 | # It takes far less time to find bugs during a code review than to test and debug code. |
||
| 4 | # 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. |
||
| 5 | # By walking another person through your code, you are no longer the only living human that understands what you were thinking! (Good for maintenance) |
||
| 6 | # 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.) |
||
| 7 | # 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. |
||
| 8 | # Code reviews provide a valuable opportunity for sharing knowledge and exchanging coding techniques. |