News


Design Patterns are something that most developers already know, but can't put a name to. Being one of those developers I decided it was about time I learnt the name of of a few more design patterns (beyond the singleton and factory patterns). Of course the Gang of Four book was on my shopping list, but I haven't read that yet so I'll save that for another blog post.

The first book I read was "Head First Design Patterns" by Eric Freeman, Elisabeth Freeman, Bert Bates and Kathy Sierra (another gang or four!). This is an excellent book, and athough it is written for the Java developer it is very easy to read as a C# developer. The style is very casual and the authors have managed to make what would otherwise be a very dry subject both interesting and informative. I would recommend anyone wanting to learn about design patterns start with this book!


Comments

Gravatar # re: Design Pattern Book
Posted by Stacy Vicknair on 12/8/2008 4:27 PM
Hey Darren,

I've been interested in reading this book, along with a long list of others (software requirements 2nd ed, stuff on UML, other random topics).

I was curious, what do you feel will improve in your code as a result of reading these patterns? Do you believe it will help you in developing an application's architecture (as in, help recognize patterns that should be used for specific situations, and help you determine and map out a full architecture without writing code).

Let me know,
Stacy
Gravatar # re: Design Patterns Book
Posted by Darren Fieldhouse on 12/9/2008 3:12 PM
Hi Stacy,

I think knowing about design patterns helps a professional developer in a few ways. First of all they give us a common language; all developers know what you mean if you say "use a for loop to do this" or "you need a recursive function to do that", design patterns extend that vocabulary so you can say "I'm going to use the strategy pattern to solve the problem" without having to go into huge amounts of details about what that involves.

The other thing about design patterns are they employ good design practices. I’m not saying that just because you use the pattern your application will be well designed, but by looking at patterns you can learn a lot about what is and what isn’t good practice.

Hope that helps...

Post A Comment
Title:
Name:
Email:
Website:
Comment:
Verification: