2 of 2 people found the following review helpful
2.0 out of 5 stars
Too much and not enough, Sep 13 2003
This review is from: Object-Oriented Design & Patterns (Paperback)
I came away from this book wondering just who was meant to read it. It starts with "A Crash Course in Java." (Somehow, I never learned to like any "crash" in the context of program design.) This is much too brief to teach the language, or even summarize it well. Any of many other books would be better for teaching Java to C++ programmers.
Next, the book goes through two chapters of object oriented design. These chapters are over in about 100 pages - again, not nearly enough time to address OO design in with any real insight. The OO paradigm is truly different from previous generations of software design, and can not be summed up in a few pages of rote rules.
Worse, the author identifies "javadoc" as a design documentation tool! It is not. Javadoc does a very good job of documenting implementation, but it documents design very badly. If you're not a programmer, trust me - implementation and design are as different as carpentry and architecture. Neither is better than the other, and both are needed to build a house. Implementation is not design, though, and the two require very different documentation.
The rest of of the book continues in an odd pastiche including:
-- ideas the programmer already needed to understand the earlier material,
-- afterthoughts on the Java language, scattered among other topics,
-- a weak discussion of design patterns, and
-- a severely flawed discussion of multithreading.
Only this last deserves attention. Multithreading is a subtle topic. It's easy to write multithreaded code, but very hard to write it correctly. The author actually does a good job of discussing interruption in threads. However, the book's description of synchronization and deadlock is so brief that it leaves me worried - student programmers might read that material and come away thinking they understood the topics. Insufficient knowledge may be worse than none at all, in this case. Most distressing, the author makes no apparent mention of "volatile" data in Java. Multithreaded applications don't need to use volatile data. The programmer MUST understand when volatility is a problem, though, and avoid it or address it directly. It is unacceptable to ignore the risks addressed by "volatile" declarations.
I can not recommend this book. It claims to address object oriented design, Java, and design patterns. I feel that it does an inadequate job on all counts.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
5.0 out of 5 stars
Wonderful!, July 8 2004
This review is from: Object-Oriented Design & Patterns (Paperback)
OK, in spite of the fact that I develop in C# versus Java and the price is steep, I still think this is a great purchase. Horstmann provides an insightful introduction into serious software development. The book provides a lot of detail that is aimed at increasing your understanding of the language (or related languages) versus simply conveying languge semantics. His introduction to patterns is fairly light (I'd recommend Metsker's "Design Patterns in C#") but solid enough. Although in many respects the material was "refresher" stuff, the prose was entertaining and I found myself picking the book up time and time again just to read a few pages.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
5.0 out of 5 stars
An ideal intro to OOD by an insightful author., Dec 4 2003
By A Customer
This review is from: Object-Oriented Design & Patterns (Paperback)
The previous reviewer sounds like he is looking for an all in one reference. Indeed, if you are a professional programmer and need a reference book, this one is not for you. However, if you're a student, new to OO programming/design or just want to add to your programming knowledge, this is a perfect book. It's designed for the classroom first (see the preface and exercises!), but is also useful for anyone who learned to program in C++ or Java and wants more sophisticated OO coverage. It is certainly not intended to teach the entire language. Rather, it assumes you already know how to program and want to learn more about Object-Oriented Design, including UML and design patterns. This is an important topic and it's never been introduced in a clearer, more intersting way than it is in this book.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No