THE EVIL TROLL WRITES A BOOK REPORT....

Perfect Software by Gerald Weinberg

I've had two books sitting on my desk at home; Perfect Software and How We Test Software at Microsoft; finished Perfect Software last night.

First of all, Michael Bolton referred to this book as a "gift to testers", and it wasn't in my case. I spent $23.95 for it.

Often, after I read a book, I sit and think about who the book was really trying to "reach" and what it was really trying to communicate. I'm an experienced tester and manager, so what I personally find valuable or interesting is different from what would appeal to someone newer to the field or not in the field at all. Sometimes I recommend books that I personally didn't find illuminating to someone else that I think might benefit more from it.

My favorite book written in the past 10 years is Lessons Learned in Software Testing. I'm telling you this to set the context; I've read pretty much everything published for the last 25 years. But I would not recommend that book to a beginning tester. And even with that one, I didn't agree with everything that had been written. The chapter on Epistemology. Ugh. But overall, what an awesome piece of work. I wished I had written it. That's about the highest praise any of us could (selflessly) bestow on the work of someone else...

Some of the things I particularly liked about that book were the humor and fact that the writing was so accessible. By that, I mean it wasn't written like a PhD dissertation. It was actually fun to read.

Perfect Software is equally approachable.

But overall, there was nothing for ME in that book. I found myself reading and nodding in agreement over most of the points. There was nothing in it that raised my blood pressure. Nothing that presented something I *thought* I knew in a new and different way. Nothing totally new to me that I could sit and think about.

I suppose, however, it started me thinking about writing in general. Do we really write to inform, to teach, to entertain, and to challenge? Or do we want a bunch of head-bobbers just agreeing with what we have to say and telling us we're great? There are a LOT of writers out there just expousing thoughts and ideas that we've heard a bizillion times before and that they know will only garner the type of responses that are positive. So what was THIS book looking for? Head-bobbers? Or to inform, teach, entertain, and challenge?

Overall, I thought it was a thoughtful and well-written book by someone that understands testing. But I'm not sure that book was written or intended for someone like me. I'm going to assume it was written to inform, teach, entertain, and challenge and therefore I think it would most benefit those that won't read it or buy it at all. Our managers and our clients. Perhaps someone newer to the field would also be inspired by some of the ideas in the book. They're certainly presented both intelligently and persuasively.

So overall, I'm out $23.95, and the experience wasn't bad. On the Wilkinson Richter Scale of Goodness, I give it a 3 out of 5...

And for those of you currently foaming at the mouth, please note that my comments have absolutely nothing to do with Gerald Weinberg's intelligence, contributions to the field, or IQ. This report is my own personal reaction to the book.

And good, bad, or indifferent, perhaps the report of one drop of water in the lake will encourage the other drops to read too and make up their own minds.

I'm currently in the middle of How We Test Software at Microsoft ($29.69) and I'll share my thoughts when I finish it. I've already noticed that Alan Pages's writing is much better than his limericks...(check out the Software Testing Club)...