Design Patterns
Design Patterns are resources used by developers and architects to solve a common problem. Beyond having a pattern, they have a common context used to share knowledge. They have a powerful tool to provide solutions reflecting also a context about the problem.
Knowing where to apply a Design Pattern to get a solution according to the problem is difficult, requires developer experience and an extensive knowledge to choose the right option. Developers in the path to take good design solutions are encouraged to learn the intent of every pattern, see implementation examples, read books and whatever to improve their skills.
Kind of Patterns
However, there are many kind of Design Pattern like the Object Oriented Patterns, Architecture, patterns to develop in Android, and other ones recommended by institutions like Microsoft to use in their systems. There are many Frameworks and technologies implementing patterns. Developers might find those proven solution designs in different contexts, varying the implementation way and usually combining them.
The Other Side
Sometimes Design Patterns are not the solution needed either applying the incorrect pattern or the problem to solve does not require one, such as practices are also known as anti-patterns.
When one design is implemented, then the systems could be more flexible and for certain types of implementations. Developers have to work with the advantages and disadvantages of the patterns selected and the benefits have to be greater or the other developers could hate you for a bad decision that produces slower development and the system is becoming more complex than usual.
Silver Bullets?
Solutions provided by patterns are proved and good developers have an insight about what happen in a part of the system. They know what and where fix something, make a change or add a new functionality. The pattern is a knowledge across systems, teams and companies, it is necessary take advantage using them.
No comments:
Post a Comment