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.
©2015, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org