Moderator: General Moderators
They are simply Best Practice solutions to common problems. They are usually stated as a problem then a solution. They have been proven by the best and brightest over the years to be a successful way to solve these problems. Though the pattern concept is not OOP specific they are very much associated with OOP and are mostly OOP solutions.Live24x7 wrote:1) Where does 'design patterns' fit in the entire OOP schema ?
Yes, because they provide a common language to talk about software problems/solutions without needing very long-winded explanations. They form a ubiquitous language to talk about these complex subjects.Live24x7 wrote:Are they necessary to know ?
Live24x7 wrote:I read yesterday that design patterns are to programming what scales are to music
kon wrote:Design patterns are great for solving common problems and to have a common ground deciding a solution with others. Of course we shouldn’t learn those and think them as golden rules, almost each programming real life problem is not as simple and distinctive as the problems design patterns solves. More over if you have in your mind a premade solution there is the danger to modify the problem fitting your solution making the all design really mess. Don’t get me wrong, design patterns have their place in our knowledge, but after knowing as many of them, test and use them where each fit , you can consider them as your programming experience and not holly grails.
kon wrote:if you have in your mind a premade solution there is the danger to modify the problem fitting your solution making the all design really mess
Users browsing this forum: No registered users and 2 guests