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.
Like this post? Get updates from my feed.
Related posts:
- Who Else Wants Better Short Term Memory? In “Talent is Overrated”, Geoff Colvin at one point...
- 3 Easy Ways to Stick to a Coding Standard When you’re writing python, you don’t need a lot...
- Makefiles are Software Too This post was inspired by recent experience with some...
- 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...