Perfect Software And Other Illusions About Testing – I am a little bit confused by this book and can't decide did I like it or not. Some chapters are good, some are too obvious. Obvious, of course, for me, maybe not for others, but I value books according to what new they can give to me.
First of all – version for Kindle on the Ebay is awful. All content is in one chapter (actually there are several chapters, but they are not formatted properly), which makes navigation harder:
There are some concrete characters in the book, with whom are made some examples. A lot of them are quite trivial and overdone, so they seemed pointless for me:
Some claims are doubtful. For example, claim, that the most important value of review is learning – for me it sounds like learning is the very last excuse why you should do review, because all other reasons doesn't fit. Usually (and I think in that case also) learning is a good side effect, not the purpose.
Update: see discussion in the comments about this item.
Another example – author categorically thinks that tester should not answer the question "Is the software ready to ship?" – I think that good tester definitely should answer this question and in modern projects roles are not so strictly divided:
But some claims are good and interesting:
Seems like this book is good for developers, who want to test and for testers, who are involved in testing for many-many years and they need to learn again how to test (with up-to-date tools and approaches). But for young testers, who are learning to test from scratch there are too many obvious and out-of-date recipes.
And beautiful parallel in the end: