3 ms·
Good grief. GoF was wildly successful. Design Patterns was of a time. We were just learning how to talk about design, the design of design. Now that methodolo
by specialist 8y ago
Good grief.
GoF was wildly successful.
Design Patterns was of a time. We were just learning how to talk about design, the design of design. Now that methodologies, heuristics, frameworks, architecture and so forth have become "democratic", it's hard to appreciate the original efforts out of context.
Concretely:
To Norvig's point, GoF style Design Patterns are just a rung in the programming language maturity ladder. Something like: patterns > idioms > libraries > syntax.
Cynically:
Design pattern implementations just add another layer of indirection. On the notion that you can, may, or should defer an architectural decision. (Opinions differ. I lean towards YAGNI.)
Metaphysically:
Mastery is like becoming a jazz musician. First you have to learn the rules before you know how to break them.
--
I started a design pattern study group in the 90s, still going strong today.
It always kinda goes like this:
First reading, mind blown.
Second reading, aha, now I see how this could be useful.
Third reading, meh, it's obvious, why we still talking about this?
Happily, progress marches forward, and there's always something new (or new again) to argue about. Rinse, lather, repeat.
--
The sole legitimate criticism is the exploitation of the design pattern zeitgeist. Here's a relevant documentary on that phenomenon. "Exit Through the Gift Shop" https://www.imdb.com/title/tt1587707 https://www.imdb.com/title/tt1587707
Weaponization, misuse, misappropriation of an idea happens every where. I worked for a guy who called everything a Decorator. One of the architects for the Kuali Foundation student project. Took me way too long to figure out he didn't know what a Decorator was. Those conversations were so confusing.
- stcredzero 8y agoTook me way too long to figure out he didn't know what a Decorator was. Those conversations were so confusing. Some of the GoF folks used to say most design patterns were just State or Strategy in disguise.
- specialist 8y agoYa. Just another layer of indirection. In most cases, it's about intent. The "architect" in this story conflated Chain of Command with Decorator. Fire brigade vs call thru. And how that impacts exception handling.