There are a number of excellent products out there to help make code reviews more effective. Today we’re going to look at ReviewBoard to see how it differentiates itself from its main competitors. ReviewBoard has been quietly improving its product since its initial release in 2009 to provide a great code review experience for teams of any size.
Long used by pilots to prepare an airplane for the every phase of a flight, it serves us in much the same way for code review.
The average suggested time to spend on a code review is between 30 to 60 minutes. So how do you find time to do anything else?
I mention static code analysis tools on a regular basis. It’s an integral part of a well-oiled code review process that ultimately brings value to the product. Let’s do a deep-dive to understand them better, their limitations, and what we can do to get around those limits.