Pablo’s Topic of the Month – April: Design Patterns

Pablo’s Topic of the Month – April: Design Patternspablos_topic

Over the next few days and weeks, the Los Techies crew will be writing a number of blog posts focused a particular subject in addition to their regular blogging.  Pablo’s Topic of the Month for the month of April is about ‘Design Patterns: Elements of Reusable Object-Oriented Software‘ (Addison-Wesley. ISBN 0-201-63361-2), the seminal book by the ‘Gang of Four’ (Erich Gamma; Richard Helm, Ralph Johnson, and John Vlissides) — heretofore known as ‘GoF’. There are quite a few patterns covered in this book and we definitely won’t get to all of them this month, but we’ll try to cover as many as we can, or at least go as deep as we can on some of the more (I daresay) important ones.

If you haven’t already, please consider subscribing to the Los Techies Main Feed so that you can see the various post from all the Los Techies bloggers.

The main feed is here:

What is a Design Pattern?

As always, Wikipedia has a pretty good start on the subject as well as another article on design patterns in general. I suggest you check that out first if you haven’t already read the book. For the feint-of-clicking out there, here’s a brief description via Wikipedia:

In software engineering, a design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations.

Most of the design patterns covered in the GoF book are applicable to .NET and worth being aware of, if not well studied. By recognizing already-solved problems when they being to arise, you can be a much more effective developer by using the solution pattern already devised and well refined by others to knock it out quickly so you can get back to solving the not already-solved problems.

Posts on Design Patterns

Since I’m just announcing this today, there are not any posts ready to go, but I will be posting them as they become available in this area. Please check back often!


Technorati Tags: , ,

About Chad Myers

Chad Myers is the Director of Development for Dovetail Software, in Austin, TX, where he leads a premiere software team building complex enterprise software products. Chad is a .NET software developer specializing in enterprise software designs and architectures. He has over 12 years of software development experience and a proven track record of Agile, test-driven project leadership using both Microsoft and open source tools. He is a community leader who speaks at the Austin .NET User's Group, the ADNUG Code Camp, and participates in various development communities and open source projects.
This entry was posted in Patterns, Principles, Programming, PTOM. Bookmark the permalink. Follow any comments here with the RSS feed for this post.
  • Another view on the definition of a Design Pattern is that it’s a plug used to fill a hole in your programming language (Command pattern, meet C#’s delegate).

    Or at least that’s how they propose it in GoF.. :-)

    Also, I’d stay away from Wikipedia on the topic of design patterns, they’ve had some pretty big blunders up on some of the GoF pages in the past (haven’t checked in a while though)..

  • @Evan – RE: Wikipedia – Yes, definitely. I’ll update the post tonight to give a warning. From my quick scan, it seemed that the landing pages for Design Patterns weren’t all that heinous, though.

    If you have any sites you recommend me linking, please drop them here and I’ll add ‘em to the main post body.