Filed under: Big Company, Development, Process, Small Company
As your developers move to team lead and management positions, they spend less time per day inside of the code. Code reviews offer them a chance to maintain an eye on their code.
Code reviews are not the most efficient way to catch bugs. Unit tests, static code analysis tools, and using -Wall I have found to find problems than reading code.
Code reviews are not a way to enforce style and format. If this is important to you, just use a formatting program to change the code (Eg. cindent).
One of the values of code reviews is architecture enforcement. If you have a good team, this should not be an issue since they’ll comply to the design and architecture. Although, if your team doesn’t comply to the architecture, code reviews may catch these mistakes.
The value of code reviews is for your team leads to keep in touch with the code, any bugs they find along the way is just gravy.