4 ms·
You want to manage complexity, but mention Design Patterns? I'm not a fan of this book. I've been in too many shops where it's become gospel and the code beco
by joezydeco 16y ago
You want to manage complexity, but mention Design Patterns?
I'm not a fan of this book. I've been in too many shops where it's become gospel and the code becomes an unnavigable swamp of singletons and factory classes and who-knows-what.
http://www.theserverside.com/tip/Evil-Design-Patterns-When-Design-Patterns-Become-the-Problem http://www.theserverside.com/tip/Evil-Design-Patterns-When-D...
- steveklabnik 16y agoAny good advice can be abused.
- loumf 16y agoA lot of people misunderstand that book. Design Patterns reduce complexity when used correctly. A good book to understand that is Refactoring to Patterns http://industriallogic.com/xp/refactoring/ http://industriallogic.com/xp/refactoring/. If you need your code to construct objects without knowing the type, then you need a factory (or other creation pattern). If you don't -- it's overkill. They are using a solution to a problem they don't have.