3 ms·
> Design patterns were meant to future proof code That's a misguided but unfortunately common view. Best practice is to refactor to patterns, don't try to div
by couchand 9y ago
> Design patterns were meant to future proof code
That's a misguided but unfortunately common view. Best practice is to refactor to patterns, don't try to divining them from the start.
> paper over limitations of your language.
See http://wiki.c2.com/?DesignPatternsAreMissingLanguageFeatures http://wiki.c2.com/?DesignPatternsAreMissingLanguageFeatures
- hinkley 9y agoWhenever anyone asks me if they should read Design Patterns by Gamma et al, I tell them to go read Refactoring. If they say they've already read it I tell them to read it again. The patterns are loosely what to do, but that's not the thing that lasts across the years and languages. Refactoring is why and how.
- geezerjay 9y ago> That's a misguided but unfortunately common view. Best practice is to refactor to patterns, don't try to divining them from the start. I would add that IIRC Martin Fowler himself, a manwho writes whole books dedicated to desing patterns and software design, is also the man behind the "monolithic design first" mantra.