Forum Discussion
mattcaron
14 years agoNew Contributor
Here's my take on it:
Rationale:
- A given product/module/subdivision/etc. should have at least two developers who regularly work on it.
- Those developers should review each others' code.
Rationale:
- You should be doing (1) anyway, if only for the redundancy of solving the "developer gets hit by a beer truck" problem.
- Given (1), each has the appropriate context with which to evaluate the changes. Sure, anyone can look for bad code constructions, but unless you are familiar with how the code works or what the application is supposed to do, you are more likely to miss logical bugs. A dedicated reviewer lacks the context in which to fully appreciate what the application is supposed to do.
Related Content
- 10 years agobartosz_qa
- 3 years agobrian_g_snell
- 11 months agoajhollo
- 3 years agoHarryS
- 11 years agolondondermatolo