Why did you force yourself to read such an inane work and then spend/waste even more time reviewing it? You need to review your priorities.
I read the first chapter review skimmed the rest and filed your report in the waste bin.
I read the whole thing, albeit with a rising sense of irk, just to see if they'd ever get around to grasping the pedagogical value of the book.
But no, the author is stuck in a narrow rut of personal loathings, and ended up publishing a pernicious and unedifying exercise in missing the point that ultimately reveals more about the reviewer than then reviewed.
The author centers his attack on the book around some literal interpretation of the problem domain that he seems very irritated about, and this distracts him from the very sound lessons the book provides about measuring and communicating OO designs.
