Thanks Craig. Good info.

>IMO, Design Patterns are mis-named. I rarely see the pattern when I design something. It's usually only after I'm working on something for a while that I see the pattern, then I refactor.
>
>Design Patterns are a standard way to define how something works. If I say "the app uses MVVM", then other devs know how that part of the app works.
>
>By using patterns, you will create better, more maintainable software. But beware, patterns can also be overused and make the code harder to understand.
>
>My favorite pattern books are:
>
>http://search.barnesandnoble.com/Design-Patterns-Explained/Alan-Shalloway/e/9780321247148/?itm=21&USRI=design+pattern
>http://search.barnesandnoble.com/Refactoring-to-Patterns/Joshua-Kerievsky/e/9780321213358/?itm=2&USRI=refactoring+to+patterns
>
>
>>I'm reading this article. http://msdn.microsoft.com/en-us/magazine/dd419663.aspx
>>
>>I know what I think "Design Pattern" means, but I'd like to hear other opinions.
>>
>>Thanks