The ultimate Download source

First of all, when you design, solve things in the simplest way possible. Your goal should be simplicity, not “how can I apply a pattern to this problem.” Don’t feel like you aren’t a sophisticated developer if you don’t use a pattern to solve a problem. Other developers will appreciate and admire the simplicity of your design. That said, sometimes the best way to keep your design simple and flexible is to use a pattern.

No one ever talks about when to remove a pattern. You’d think it was blasphemy! Nah, we’re all adults here, we can take it. So when do you remove a pattern? When your system has become complex and the flexibility you planned for isn’t needed. In other words, when a simpler solution without the pattern would be better.

Design patterns are powerful, and it’s easy to see all kinds of ways they can be used in your current designs. Developers naturally love to create beautiful architectures that are ready to take on change from all directions.

Resist the temptation. If you have a practical need to support change in a design today, go ahead and employ a pattern to handle that change. However, if the reason is only hypothetical, don’t add the pattern. It’s only going to add complexity to your system, and you might never need it.

Tags: head first design patterns

Also:

• Design Patterns: Elements of Reuseable Object-Oriented Software
• Bitter Java
• Java Programming Ebooks 2008
• Low-Noise Electronic System Design
• The Art and Science of Analog Circuit Design (EDN Series for Design Engineers)
• The Principles of Beautiful Web Design - SitePoint
• Tuning Car Studio 2008 - customade your car
• Hotel Design Magazine December 2008
• SOLIDWORKS 2007 BIBLE
• The Principles of Beautiful Web Design