Using design patterns again assumes a thorough knowledge of an OOP language as well as OOP principles. This is another situation where you might want to acquire a book or two. Don’t be overwhelmed by the number of design patters there are to learn; pick one that makes sense to you, and just concentrate on that one pattern, for now. Once you’ve learned one, you’ll learn the others more quickly. But remember: With design patterns, it’s important to understand the types of situation that each pattern addresses. Don’t try to learn the pattern and then figure out what it’s used for. Know what problem you want to solve first and figure out which pattern might help.
Articles:
How to Write Software Just Once
Implementing the Singleton Design Pattern
Synchronize Data Among Objects with the Publish/Subscribe Design Pattern
Coordinate User Interface Development with VB.NET and the MVC Pattern
Writing Advanced .NET Remoting Client (using the Factory pattern)
Programming with Class: Avoid Writing Tedious, Boring Code
Newsgroups:
DevX design.architecture Discussion Group
Book:
Design Patterns, by Erich Gamma, et. al.
