The Problem With Design Patterns

22 באוגוסט 2008

3 תגובות

My blog has moved. You can view this post at the following address:

הוסף תגובה
facebook linkedin twitter email

כתיבת תגובה

האימייל לא יוצג באתר. שדות החובה מסומנים *

3 תגובות

  1. Eyal22 באוגוסט 2008 ב 8:17

    The design patterns exist in order to allow devlopers and architects to talk about the technical solution in general term using well defined vocabulary whithout getting to deep into the implementaion.
    An expirience dev. or arch. will know when to use design patterns and when not.
    XP lectures that the development should be gradual and inremental – starting from the simplest solution and advancing to more complex when needed – one who knows design patterns and understands the problem they were ment to solve will know that in future, when refactoring, he can use DP x or DP y and impement them when absolutly needed knowing and dealing with domain specific limitations and issues.

    To wrap it up – I think that gradual and incremental development will reveal you when your code smells and needed to be refactored using DP or whether to use other self-invented solutions.
    P.S. you might think you invented the solution but there's a big changes that you just thought of an unusual implemintation for a known design patter.

  2. Yoni Rapoport22 באוגוסט 2008 ב 13:41

    I think Design Patterns can be a part of a developer's vocabulary and should be used without hesitation. "Bending" a use case to fit a Design Pattern is similar to "bending" a software condition to fit the "if" statement… Design Patterns are the tools of the software designer and, whether intentionally or not, well designed software will end up using Design Patterns.

  3. Paul W. Homer24 באוגוסט 2008 ב 12:52

    Focusing on producing simple, consistent and readable code, without getting to dogmatic about what is "right", will almost always produce a better result than strictly following a limited set of rules. Elegance comes from what is, not how we created it.