Peer Review
Learning Objectives
- Define fault, error, and failure
- Illustrate how reviews alter effort across the software development life cycle
- Contrast “lightweight” peer review with formal reviews
- Critique source code to improve the implementation of a software system
How to Complete this Lesson
Complete the following learning activities: (1.25 hours total)
- Read “Clean Code Isn’t Enough: It Must Be Crystal Clear, Too” (5 minutes)
- Read “Don’t waste time on Code Reviews” (15 minutes)
- Watch Code Review on GitHub (2 minutes)
- Attend the class meeting (60 minutes)
Resources
Further Reading
Karl E. Wiegers, “Humanizing Peer Reviews,” Software Testing & Quality Engineering, March / April 2002
Robert Fink, “Code Review Best Practices,” Palantir (blog), 4 March 2018
Videos
- Peer Review Overview and Anti-Patterns (2 minutes)
- Most Effective Software Quality Practices (2 minutes)
- Peer Reviews Are Effective and Efficient (3 minutes)
- Fagan Style Inspections: The Gold Standard (4 minutes)
- Rules for Successful Peer Reviews (4 minutes)
- Perspective-Based Peer Reviews (2 minutes)
- Peer Review Checklist Template (template) (4 minutes)
- Peer Review Case Study - Course Project (5 minutes)
- Review Everything in the Vee – not just code (1 minute)
- Peer Review Economics (3 minutes)