Since the GoF, there are quite a few more publishments on Design Patterns. However, none of them can be as influncial as the GoF. Don't we need more design patterns?
In my opinion, the GoF revealed some of the fundamental principles/criteria for a good OO design. The key is how to distribute information/data and responsibility/code among different classes/modules in such a way that
1. foreseeable changes are made easy and
2. conceptual behaviour and actual implementation are decoupled.
Design patterns are examples where these principles are applied properly. Once you understand these principles and are able to apply them to real world design issues, more examples/patterns will certainly help you to enhance the understanding of these principles but the impact is becoming marginal. That is probably why none of the later publishments can be as influncial.
Friday, December 11, 2009
Wednesday, December 9, 2009
Agile without Architecture?
Being Agile is good but without a collective architectural view of the product, it may easily become cowboy development where each developer just does what he/she thinks is right. When that happens, architectural integrity can be easily lost. In this sense, the function of an architect is essential to the success of Agile development. This function may be performed by an individual or by a collective effort.
Subscribe to:
Posts (Atom)