Prerequisites for Effective Code Review
Editorial Note: this is a post that I wrote originally for the SmartBear blog. You can read the original here, at their site. You should check out the posts by some of the other authors over there as well.
I’m betting that, at some point in your travels, you’ve seen a blog post or a document in a software shop that details prerequisites for good code review. It probably contains items like, “make sure you’ve run all the unit tests” and “make sure you’ve given the reviewer(s) enough notice.” This information certainly has value, but it’s not what I want to talk about today.
Today, I want to talk about prerequisites for effective code review culture, rather than prerequisites for an actual code review. The question thus is not, “are you prepared for this code review?” but rather “is your group prepared for code review, in general, to be as effective as it can be?”
Asking a question like this makes sense, if you stop and think about it. A director of software engineering can’t one day stroll through her group’s team space, declare, “Alright, folks, start doing code review,” and expect awesome productivity to follow straightaway. Various elements of preparation are necessary, first.