Design Patterns in Java (paperback) (Anglais) Broché – 18 avril 2006
|Neuf à partir de||Occasion à partir de|
|Broché, 18 avril 2006||
Description du produit
Présentation de l'éditeur
Design Patterns in Java™ gives you the hands-on practice and deep insight you need to fully leverage the significant power of design patterns in any Java software project. The perfect complement to the classic Design Patterns, this learn-by-doing workbook applies the latest Java features and best practices to all of the original 23 patterns identified in that groundbreaking text.
Drawing on their extensive experience as Java instructors and programmers, Steve Metsker and Bill Wake illuminate each pattern with real Java programs, clear UML diagrams, and compelling exercises. You'll move quickly from theory to application—learning how to improve new code and refactor existing code for simplicity, manageability, and performance.
- Using Adapter to provide consistent interfaces to clients
- Using Facade to simplify the use of reusable toolkits
- Understanding the role of Bridge in Java database connectivity
- The Observer pattern, Model-View-Controller, and GUI behavior
- Java Remote Method Invocation (RMI) and the Proxy pattern
- Streamlining designs using the Chain of Responsibility pattern
- Using patterns to go beyond Java's built-in constructor features
- Implementing Undo capabilities with Memento
- Using the State pattern to manage state more cleanly and simply
- Optimizing existing codebases with extension patterns
- Providing thread-safe iteration with the Iterator pattern
- Using Visitor to define new operations without changing hierarchy classes
If you're a Java programmer wanting to save time while writing better code, this book's techniques, tips, and clear explanations and examples will help you harness the power of patterns to improve every program you write, design, or maintain.
All source code is available for download at http://www.oozinoz.com.
Biographie de l'auteur
Steven John Metsker, passed away in 2008 and was a Managing Consultant with Dominion Digital, an information technology and business process reengineering company. Steve specialized in object-oriented techniques for creating clean, powerful software, and he is the author of Building Parsers with Java™, Design Patterns Java™ Workbook, and Design Patterns in C# (all from Addison-Wesley).
William C. Wake, http://www.xp123.com , is an independent software consultant, coach, and trainer with more than twenty years of programming experience. Bill previously held positions with Capital One Financial, DMR Trecom, and VTLS, Inc. He is the author of the Refactoring Workbook and Extreme Programming Explored (both from Addison-Wesley).
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.
Détails sur le produit
Si vous vendez ce produit, souhaitez-vous suggérer des mises à jour par l'intermédiaire du support vendeur ?
Meilleurs commentaires des clients
Un problème s'est produit lors du filtrage des commentaires. Veuillez réessayer ultérieurement.
Commentaires client les plus utiles sur Amazon.com
I would not recommend this.
An earlier reviewer commented that the format/structure is a problem - I also found it annoying. I dislike authors that play pantomime with complex topics like this. Further, when my mind is in computer mode the often used sentences in this book like "if you want to ..." confuse my subconscious learning brain. This is because I may not "want" but may "need" - and I need to figure out why/if/when I may want this thing. I feel that this indicates that the authors are not confident in concisely explicating a complex topic.
Some things grate, for example the Singleton Pattern is classified differently (Responsibility Pattern) here to the GoF book (Creational Pattern). I don't see the communicational point in messing with the acknowledged but the perhaps disputed GoF masters (Design Patterns) and their accepted wisdom.
Technically this book does not appear complete. In discussing thread safety for the Singleton the book provides a synchronized example but not a "double-checked locking" example as does Head First Design Patterns (Head First). The double-check reduces the use of synchronization in a frequently accessed singleton and speeds things up dramatically. Omissions like this don't inspire confidence.
The book feels light in Java code examples. It is not a clear Java focussed exposition on patterns. It does not provided comprehensive Java examples on common patterns to insert in production (where I am personally at now). It seems a missed opportunity because I wished so much.
I was hoping to outgrow my Head First(HF) experience, but this book does not do that. I would recommend the HF book over this one - even if you are annoyed by the HF style. HF seems to have been more thought out.
This book added little to the GoF and HF books I have read.
This book maybe useful for Java programmers who have not been exposed to patterns or for undergraduate classes.
The authors use examples from rocket science to explain the concepts in the book. They could have picked simple day-to-day examples like a library or a movie store. But instead decided to use rocket science. Then there is something called Oozinoz. I don't get exactly what that is or how it is relevant to Design Patterns. But the authors use that a lot. If what I have written sounds vague, well that is because it is.
Secondly, the organization is very bad. The meat-and-potato of the learning is hidden away in "challenges." Let me explain. At the beginning of every chapter, the authors briefly explain the problem to you. Then instead of providing a solution, they throw a challenge to you to solve the problem. To view the solution one has to flip to the back of the book where it is provided in vague esoteric diagrams. This is not the way to write books.
There are 23 patterns allegedly described in this book. I haven't understood any of them. The few I knew from before like Singleton and MVC, I am now more confused about them. I wish I could get a refund for this trash.