Why Code Reviews Aren't Popular| August 2008 | ||||||
|---|---|---|---|---|---|---|
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | |||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| 24 | 25 | 26 | 27 | 28 | 29 | 30 |
| 31 | ||||||
Why Code Reviews Aren't PopularCode reviews are almost universally recognized as the most effective way to improve the product. Why are they done so rarely? Short answer: the participants don't get sufficient immediate, concrete payback proportional to the cost and effort involved. Sure, the system, the team benefits, but the individuals involved calculate the equation as a net negative.
Harnessing the value of code reviews will take developing new practices that balance the cost to the developer with greater individual benefits.