Top critical review
9 people found this helpful
Hard Work and not worth the money
on 13 January 2003
The patterns start in chapter five. Ignore the rest of the book on pain of absolute boredom. For example chapter two (32 pages) defines the keywords to be used in catagorising the patterns. Chapter three (9 pages) defines all the ways that patterns are ever written up, probably in order to justify changing it in this book. I notice that most or all the good reviews are by management and consultants, so maybe it works better for them, but I found the engineering antipatterns too few in number and too obvious in solution. Instead try Deathmarch Projects, Writing Solid Code, and Debugging the Development Process. They don't have the magic word "pattern" in the titles, but they're a lot more use.