How's My Code?

Why do code reviews?

Because they increase the quality of your code. They catch the nasty logic errors that your tests missed. They make sure everyone follows the best possible coding practices.

And, in the eventual case a shark eats one of your teammates the moment code he wrote breaks in production, you will have a fairly good understanding of what was going on with that code, and why it might be breaking, because you read it, as well as the rest of the team.

But don't take our word for it, here's what Jeff Atwood, of Coding Horror and Stack Overflow fame, wrote about why he can't live without code reviews:

I believe that peer code reviews are the single biggest thing you can do to improve your code. If you're not doing code reviews right now with another developer, you're missing a lot of bugs in your code and cheating yourself out of some key professional development opportunities. As far as I'm concerned, my code isn't done until I've gone over it with a fellow developer.

Jeff Atwood, on “Code Reviews: Just Do It”