Most programmers agree that it's easier to prevent technical debt than it is to pay it off. And one of the best ways to prevent sub-par code from ever seeing the light of day on a production box is to have a solid code review system in place. Over the years, I've discovered some practices that have really made a difference for me. Here's the first in a series.
Although it's traditional to have the technical lead be the "gatekeeper of the code", I believe everyone on the team should participate by reviewing the code. Here's why:
