Top critical review
20 people found this helpful
Good information hidden in bad explanation
on 22 October 2013
I am very mixed up about this book... most other devs I know appear to have read the shortened version (I hear this means the bits in bold) and understand it perfectly. I find it hard to believe, as there's so much more information in the non-bold bits that to read just the bold bits would be totally misleading.
However, I find this book so hard to read at the same time. It's a great topic and all developers need to understand this modelling technique properly as this is the basis of the new age of software development. But it lacks analogies and a range of examples to better explain what he means, which means that he uses a very terse descriptive that is hard to process. I think several people should've written it and put in their experiences of the approaches they used and their experiences.
The first quarter of the book is particularly annoying as it talks about what you are about to learn all the time. I think he also means for it to be used as a reference, but it's far too verbose and waffly and not split up enough conceptually to be useful for that.