Title: Nice to know, but too complicated, abstract and unpragmatic
Review: This book has some value even today, but I was quite bored during reading this book. I often noticed that Fowler has gift of describing simple things in complicated (and boring) ways, which happened many times in this particular book. I felt like this book was born in those "pattern days" where everyone tried to create own patterns on everything in the world. Fowler tries to describe some common domain problems and introduce various patterns that are supposed to deal with them.Some of them are quite nice and good at least to think about, but other were explained in very abstract manner, with weird (pre UML) pictures of often over-complicated problematics that poorly illustrated the domain problem.If your job is programming, you won't miss much if you ignore this book. If you are analyst, you should at least consider it, but it still isn't what you call "must read".
Is this product review negative?