Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Best Kept Secrets of Peer Code Review: Modern Approach. Practical Advice. (Modern Approach. Practical Advice.) Paperback – January 1, 2006
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Customers who bought this item also bought
What other items do customers buy after viewing this item?
Ten practical Essays from industry experts giving specific techniques for effective peer code review.
Top customer reviews
I'm happy to say that my doubts are addressed - not banished utterly, but faced head on. Despite a bit of jargoneering (is "trial" really a verb?), the authors present updated techniques that appear to reduce some of the problems working against effective inspections. And no, the techniques don't demand that you buy their product first. The techniques dovetail well with modern ideas, including the Law of Demeter (p.46, on module coupling), SEI's PSP, and the rich IDEs common on developers' desktops today. Finally, the last chapter - and only the last chapter - addresses the company's product.
Despite the book's commercial origin, it has lots of great information beyond the writers' product. In fact, it reminds me of "Planecraft," written over 70 years ago. That book was written as a sales tool for the greater corporate glory of a company selling woodworking planes, but has enough worthwhile technical content that it was reprinted a few years back. Maybe "Best Kept Secrets" won't last 70 years, but I was struck by the analogy.
The book's discussion discussion is wide-ranging, readable, and helpful. A few editing glitches put potholes in the reading path, but only a few. On the whole, I came away somewhat more willing to throw myself back into the fray of inspections, as long as they're run carefully, in accordance with many of the ideas shown here.
//wiredweird, reviewing a copy given out as conference swag
Turns out I was wrong. Although the tone of the introduction had me worried, once the book started I found it quite interesting and informative. The book uses a number of studies to make a good case for why (lightweight) code review should be used as a development practice. The suggestions were backed by research data that they analyzed and discussed, and they did a good job of explaining their conclusions with the prose.
I would recommend the book to anyone who is interested in the software development process or who cares about delivering quality software.
Despite having been in IT for some fifteen years now, I must admit I'd never heard of peer code review before Smart Bear Software's book landed on my doorstep. I have to say it's a pretty darned good idea, though, from what I've read of it here. I'm not entirely sold on the book itself, but I like the idea it's touting, which is basically this: two (or more) sets of eyes on a given piece of code are better than one.
As for the book, it's pretty obviously another marketing tool for Smart Bear's code review tool, which makes me like it less than I otherwise would, probably. However, if you're a complete novice who's just being introduced to the idea, there's a good bit of valuable information here; it's worth reading as an overview of peer code review. Obviously not a general-audience book, but if you're in IT, check it out. ***