Menu
Are there, in the canonical Gang of Four list, any design patterns that you often find misused, misunderstood or overused (other than the highly debated Singleton)? In other words, is there a design pattern you would advise to think twice before using? (And why?)
257
Common Mistakes while Implementing Facade Design Pattern Just naming a class as ABCDFacade. java doesn'r really make it a facade. Creating a java class and 'forcing' the UI to interact with other layers through it and calling it a facade layer is one more popular mistake.
They are not. They are ways to communicate and think about useful programming ideas.
The problem describes when to apply the pattern. It explains the problem and its context. It might describe specific design problems such as how to represent algorithms as objects. It might describe class or object structures that are symptomatic of an inflexible design.
Disadvantages. Using design patterns requires extensive knowledge. Having design patterns available can also lead to people believing that apparently all problems can be solved using existing design patterns. In short, this can limit creativity and the desire to find new (better) solutions.
Factory Patterns...
I was parachuted into a project before where every single MyObject in the system had an equivalent MyObjectFactory for generating new instances. There was no concept of abstraction or extended classes... just plain old ClassX & ClassXFactory.
And no-one could explain why... "It was just the way things had always been done"
164
The singleton pattern .. global state often leads to problems when testing
Any code depending on the singleton gets harder and harder to test because that dependency isn't easily mocked..
40
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
