Nov 25, 2009
One Simple Step for Avoiding Shallow Reviews
We’ve all been guilty of giving a shallow review: “Looks ok.”
Given typical defect densities, any non-trivial design or code is going to contain some errors. Even seemingly trivial maintenance fixes are likely to be defective.
It’s your job as a reviewer to find as many of these defects as possible. If you’re not finding defects, you’re wasting your time on reviews.
That “one simple step”? Remind yourself that there are almost certainly defects in the work product you’re reviewing, and then find them. It’s all about attitude.
Related posts:
- Who Else Wants Better Short Term Memory? In “Talent is Overrated”, Geoff Colvin at one point...
- 9 “Must-Have” Tools for Software Teams The items below are useful systems based on my...
- Insist on Automatic Tests At some point your team is going to be...
- Data vs Code I’ll take an array over a giant switch-case statement...
- An Interesting pid File Race ISC’s dhcpd uses this code to check for an...