July 20–24, 2015
Portland, OR

Getting the most out of code review

Stephanie Wagner (Namely)
2:30pm–3:10pm Thursday, 07/23/2015
Collaboration E 143/144
Average rating: ***..
(3.30, 10 ratings)
Slides:   external link

A nearly ubiquitous concern with code reviews is that they consume resources otherwise available for active development. We begin by analyzing the typical goals of a code review: reduction of bugs, adherence to established coding standards, security hardening, etc. We then explore several additional benefits that make spending these resources overwhelmingly worthwhile. Chief among these is the opportunity to build a stronger team of developers via a workflow that encourages discussion and learning.

Developers often receive no instruction on the ins and outs of code reviews, leaving them to copy inefficient behaviors. Not all teams have well established (or enforced) coding guidelines, resulting in poorly matching code that’s difficult to read. You’ll learn how to tackle these issues on a team-­wide level, and establish clean, efficient procedures that result in tangible benefits for your organization.

We’ll cover:

  • The goals of a peer review
  • How well those goals are being met in your organization
  • What to look for during a review
  • Optimizing time spent on reviewing code
  • The importance of a consistent coding style
  • Giving constructive feedback
  • Group code reviews
  • Who should participate in code reviews?
Photo of Stephanie Wagner

Stephanie Wagner

Namely

Stephanie Wagner is a software developer based in New York City. She is currently a Rails developer at Namely, a startup providing cloud­-based HR software for growing companies. Her love for programming started with creating simple Flash games at the age of 13. In high school, she focused on learning web development using PHP, Javascript, and MySQL. Stephanie is an active participant and volunteer at several developer­-centric organizations, such as Women Who Code.