Design Patterns

Chris Nolan · 15th September 2002, 10:19 PM

Nothing here.

Geo · 15th September 2002, 10:44 PM

Yeah, I use design patterns. Probably the most common ones I use are Singleton, Factory and Strategy.

Singleton is just a really useful pattern, I find it is appropriate for something in just about every system I develop of any reasonable size.

So far I have found design patterns to be a useful tool to structure a system, provided that you stick with the correct pattern for the correct context and dont try to bend a context to fit the pattern.

Silent8ob · 17th September 2002, 2:05 PM

I'd probably answer that "Yes" I use patterns in OO design - but not in what I'd call a conventional manner.

I think all programmers that do a lot of OO design use patterns to an extent, although many times without knowing it.

In so much as the "Patterns" are just nice names for the "tools" or "tricks" they've built up in their design experience over the years.

Having studied patterns though, you get a nice big "toolbox" to approach OO design problems, without having gone through the years of work needed to aquire them through real world experience.

To answer the second question, design patterns do provide an extra level of abstraction over "normal" OO design, which can only be a good thing, in terms of structuring design space.

That said, I'd prefer someone to be disciplined in their design, before subscribing to any particular design methodology. The longer I'm around, the more I believe that Discipline is everything in this field

D.

15th September 2002, 10:19 PM	#1
Chris Nolan Member Join Date: Jun 2001 Posts: 908	Design Patterns Nothing here. Last edited by Chris Nolan; 11th October 2007 at 6:44 AM.

15th September 2002, 10:44 PM	#2
Geo Member Join Date: Jun 2001 Location: Adelaide Posts: 2,377	Yeah, I use design patterns. Probably the most common ones I use are Singleton, Factory and Strategy. Singleton is just a really useful pattern, I find it is appropriate for something in just about every system I develop of any reasonable size. So far I have found design patterns to be a useful tool to structure a system, provided that you stick with the correct pattern for the correct context and dont try to bend a context to fit the pattern. __________________ "That's the way good software gets designed. So if you pull out a piece it won't run" - Steve Ballmer Last edited by Geo; 15th September 2002 at 10:47 PM.

17th September 2002, 2:05 PM	#3
Silent8ob Member Join Date: Jan 2002 Location: Perth Posts: 909	I'd probably answer that "Yes" I use patterns in OO design - but not in what I'd call a conventional manner. I think all programmers that do a lot of OO design use patterns to an extent, although many times without knowing it. In so much as the "Patterns" are just nice names for the "tools" or "tricks" they've built up in their design experience over the years. Having studied patterns though, you get a nice big "toolbox" to approach OO design problems, without having gone through the years of work needed to aquire them through real world experience. To answer the second question, design patterns do provide an extra level of abstraction over "normal" OO design, which can only be a good thing, in terms of structuring design space. That said, I'd prefer someone to be disciplined in their design, before subscribing to any particular design methodology. The longer I'm around, the more I believe that Discipline is everything in this field D.