Some of the recommendations made in this book could be used by the editor or by the author on this book itself. Maybe SIGS & the author could apply some techniques from a business jargon called "quality management".
1. The editing is atrocious. There are so many incomplete paragraphs missing from the text e.g. page 106, the paragraph ends in mid sentence, "you increase the productivity of your p" (litterally the p is the last letter in the paragraph). This book is filled with such sloppy editing.
2. Bad Editing is obvious when we look at the diagrams. No one has taken the time to make them presentable in a book format. Some diagrams have text flowing out of a box. Some diagrams are not even related to the text. They seemed to be inserted because they were simply available.
It's sad to see a potentially good book ruined by sloppy editing.
3. In terms of content, I found there are many good ideas in the book but it is organized terribly. Once we got the thesis that OO development is "serial in the large" & "iterative in the small" and to combine various object-oriented design & analysis techniques, then we are lost in many disorganized details. If the author has concentrated on the two theses above, the book can be very useful.
4. It is obvious that the author has done much oo development and really want to convey his exeperience to the readers. But if you are looking for process patterns that can be applied in your work, there are not many from this book. A lot of anecdotal, amusing stories, but few "process patterns".
5. The book is more of a mind-dump from the author's lecture notes. He kept promise to provide real-world development examples and away from the "theoretical, ivory-towered", but I feel like what we got is what the author think about the original ideas of other object-oriented experts.
