+972 52-548-6969
Patterns vs. Blueprints
time to read 1 min | 105 words
Recently I had several discussions about the usage of patterns, and application thereof. Usually, there are recommended implementation for a pattern, often this is the way it is presented in its pattern catalog.
The discussion had to do with the amount of fidelity that you had in implementing the pattern. My view on that is that the usage of a pattern doesn't require a one to one match with the common implementation, but leave room for change while keeping the concepts of the pattern in use.
Patterns are the overall shape of the solution, they are not a blueprint, to be slavishly followed.
Comments
Agreed! We should keep in mind that the implementations shown for many of these patterns were conceived over ten years ago. Since then we've found many different ways of achieving similar behavior. Consider the IFetchingStrategy<T> thing in Rhino.Commons; this is the Strategy pattern, but the context in which it is used is not as tightly coupled to the implementations of the strategy as the original GoF example.
Comment preview