Today, so many projects, both open and closed source suffer from lack of quality. Many of us are aware of the importance of testing in our development processes, but code review is something that is often overlooked or misunderstood.
What does it mean to review code? Find bugs? Complain about tabs vs. spaces? Or something more? Code review is about quality, humility and sanity checks, and a good one takes some skill to do right. I will go over some tips I have found useful over the years doing code reviews.
I was responsible for moving a large part of Comcast over to doing pre-commit code reviews using git and gerrit. Team by team, I helped transition developers from a culture of not reviewing code to making code reviews and testing second nature. I have given this talk at local conferences (CPOSC) and user groups, and believe the benefits of good code reviews are under-represented in the developer community.
I cannot stress enough how much good code review practice has changed the way we work for the better, and would love the opportunity to share that knowledge with the world.
