We use the Strategy pattern all the time (some knowingly and some by some sort of fluke).

Here is a nice a way to implement Strategy without the overhead of interfaces. It’s a bit anti-OO, but is useful when there is no concrete need to create a new type just to perform some logic.

http://www.lowendahl.net/showShout.aspx?id=115

Unless you are applying design techniques to your unit tests, they can become quite messy. In such cases, being familiar with these anti-patterns can help you stay away from trouble.

http://blog.james-carr.org/?p=44

I really love Martin Fowler’s architecture patterns. Here is an article covering a few basic patterns from his fascinating book - Patterns of Enterprise Application Architecture.

http://www.evanhoff.com/archive/2007/02/14/Basic-Application-Patterns-Transaction-Script-Domain-Model-and-Table-Module.aspx

http://devlicio.us/blogs/jeff_perrin/archive/2006/11/16/a-modified-snapshot-pattern.aspx

A very handy pattern. Well, maybe not that handy, but still neat.

http://devlicio.us/blogs/jeff_perrin/archive/2006/12/13/the-specification-pattern.aspx