Pattern Hatching: Design Patterns Applied

by John M. Vlissides

Book Overview

Design patterns, which express relationships between recurring problems and proven solutions, have become immensely popular in the world of software development. More and more software developers are... This description may be from another edition of this product.

• Format: Paperback
• Language: English
• ISBN: 0201432935
• ISBN13: 9780201432930
• Release Date: June 1998
• Publisher: Addison-Wesley Professional
• Length: 160 Pages
• Weight: 0.85 lbs.
• Dimensions: 0.4" x 7.4" x 9.2"

Customer Reviews

Patterns Demystified

GoF presents everything you need to start with patterns. This one tells how to identify a pattern when it's cooking. It explains in actuality what patterns can and cannot do, what patterns are and are not, how does a pattern come to existence and stuff related to the concept of patterns and not a list of patterns as in GoF.GoF is if you need to dive into patterns. This one if you need to swim in patterns. Don't expect a list of patterns as in GoF. This is more on how to identify a pattern, how to chose among a set of patterns, when to use, when to invent and etc.This book will serve best after the pattern hype has washed over you atleast once.

An essential companion to the GoF book

A succint and lucid explanation of how patterns can be actually applied. Chapter 2 is a must read where John develops a file system application - he dwells in great detail about which patterns suit best the needs of the application and which do not. He starts with the Composite pattern, then refines the model gradually with Proxy, Visitor, Template method, Abstract Factory, Singleton and Mediator patterns. The 3rd chapter introduces a new pattern called 'Generation Gap' while the 4th chapter is an extremely entertaining read containg numerous excerpts of correspondences between GoF authors where they debate whether the MultiCast pattern is just a refinement of Observer or a pattern in its own right. IMHO - read the basic patterns in the GoF book first, read chapter 2 of Pattern Hatching, go back and read the GoF book again. Do this a number of times and you'll probably have a much better insight than by just reading the GoF book. A word of warning for Java developers - it would help to have a decent knowledge of C++ (templates included ;-) ) to understand the code samples.

A Necessary Book

This slender volume should be required reading for anyone working on an object oriented system (and if you're using C++, you ought to read it three or four times). This book won't so much tell you how to solve particular problems as much as it will help to develop a way of thinking about programming problems that leads to well-design solutions.The GoF book's second chapter example is unfortunate: virtually every programmer I've recommended Design Patterns to has expressed frustration over the inaccessibility of the primary example of applying patterns in a system.The file system example in Vlissides, on the other hand, is a lucid and enaging narrative that everyone relates to and seems to gain immediate insight from. I now recommend this book as a requirement for really understanding the GoF book. It's worth the price many times over.

The key word is "Applied"

Although I was familiar with the GoF patterns before I read "Pattern Hatching", John has given me a whole new perspective on their use. "Pattern Hatching" showed me how to use the patterns in a generative way. In the past I used patterns to explain a design I came up with through "intuition". But using the patterns to generate the design has improved the final outcome.Now I have a better understanding of the role of patterns in the development process.John has an easy to read style which makes the material very accessible. The length isn't daunting either. You should certainly spare the time to read this.

I couldn't put it down.

If you liked the "Gang of Four" book (Design Patterns: Elements of Reusable Object-Oriented Software, by Gamma et al.), you will love this book. Mr. Vlissides has an execellent writing style that is very engaging for this type of material. Besides going into some additional design patterns, and some pattern strengths and pitfalls, you get a facinating behind the scenes look at what went on in the development stages of the original Design Patterns book.Chapter 2 of the book ("Designing with Patterns") is the best written example of how patterns are used in practice that I've ever seen. That chapter should be required reading for anyone who is confronted with having to create software designs but doesn't know where to start in making various design tradeoffs.When I got the book, I was consumed until I had read it from cover to cover. If you are interested in design patterns, you will probably feel the same way.