While nearly every development team uses some form of code review, code reviews are frequently used only among developers. While other developers are certainly a valuable audience for your code, nondevelopers can also add value by applying their own perspectives to the work as early on in the process as possible.
Margaret Fero explores the benefits of having representatives from the product management, technical documentation, instructional design, user interface design, and user experience teams on your code review from the start, rather than starting with just developers and adding other teams’ considerations later in the process. A code review is cross-functional if it includes not just members from other teams but also acceptance and implementation of the different types of feedback. She suggests different functional roles that could be included in a code review and what each role can add to the overall success of the review. Margaret explains the benefits of different perspectives and general best practices for choosing your code reviewers (either at the process development level or implementation level) and addresses some relevant change management issues.
Margaret Fero is a technical writer at Degreed, where she enjoys helping users track all of their skills regardless of how those skills were developed. Previoiusly, she documented software for containerized freight shipping.
For exhibition and sponsorship opportunities, email email@example.com
For information on trade opportunities with O'Reilly conferences, email firstname.lastname@example.org
View a complete list of OSCON contacts
©2019, 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. • email@example.com