Moonwraith
OSNN Veteran Addict
- Joined
- 22 Oct 2004
- Messages
- 1,133
Now this is a last second ditch attempt to try and understand WHY design patterns are actually useful? I've got notes, and plenty of internet sources that can explain all of them in the typical verbose ways.
But my question is, to anyone out there with experience with java design patterns, (and also the skill to translate it into retard speak for me).. Why _DO_ these stupid design patterns help with the re-use of code?
I've used some specific ones before, and they just merely complicated the system for almost no reason.
The key ones to focus on are... Factory method. Abstract factory, Singleton, Adapter, Observer, Composition, Façade, State and Strategy patterns.
Factory methods, singleton, facade and adapter are relatively straight forward.
If there's no one out there that can help or doesn't have the time by tomorrow, then don't worry about it - exam tomorrow and my mind's finally caved in on itself. :dead: I'm pretty much doomed either way, but who knows, there may be some genius out there
But my question is, to anyone out there with experience with java design patterns, (and also the skill to translate it into retard speak for me).. Why _DO_ these stupid design patterns help with the re-use of code?
I've used some specific ones before, and they just merely complicated the system for almost no reason.
The key ones to focus on are... Factory method. Abstract factory, Singleton, Adapter, Observer, Composition, Façade, State and Strategy patterns.
Factory methods, singleton, facade and adapter are relatively straight forward.
If there's no one out there that can help or doesn't have the time by tomorrow, then don't worry about it - exam tomorrow and my mind's finally caved in on itself. :dead: I'm pretty much doomed either way, but who knows, there may be some genius out there