I can't help but notice the amount of design patterns that are out there.
Does anyone have suggestions on an order I should learn them in? Or should I pick and choose them at random?
The only one I know, so far, is singleton.
Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this communityI can't help but notice the amount of design patterns that are out there.
Does anyone have suggestions on an order I should learn them in? Or should I pick and choose them at random?
The only one I know, so far, is singleton.
When you only consider the gang of 4 design patters internally at my company we have a design pattern training that has the following order, it works pretty well. Sometimes you need one to learn the other and vica versa.
Day 1
Day 2
Day 3
Day 4
Extra:
But when you want to learn them I would just start with the Head First Design pattern book (not just really my opinion, but its also seems to be the standard answer for these kind of questions) and follow that with the gang of four design pattern book. Those two together should give you all the order you need.
I wouldn't be so concerned about learning design patterns in a specific order.
In my opinion, here are the first two steps that you should take when learning design patterns:
Dofactory has a very nice organization of design pattern, including the UML diagrams as well as sample code. They also have Frequency of use
scale, which identifies how popular the pattern is. So, I'd suggest you to browse their webpage.