There are as many ways to conduct code reviews as there are to skin a cat. Some methods are more pleasant than feline taxidermy, some less so. At work, we’ve found a code-review method that has been relatively pain-free while still providing significant benefits: Check-in Code Reviews.
In a nutshell, before a programmer checks any significant code changes into source control, we have them get a quick (usually less than 5 minute) code review from one of their colleagues. In the process, they’re expected to explain roughly how their code works and why they implemented what they did. The reviewer than offers comments and advice (if they have any) and up the code goes to server-land. That’s pretty much it. It’s simple to the point of being trivial, but it has worked out well at work. Here’s why:
![code_review[5]](http://gamedevwithoutacause.com/wp-content/uploads/2012/03/code_review5.jpeg)


