Doing Patterns

Michael Earls has a post about a co-worker who doesn't do patterns.

I can understand both sides of the argument here.

Patterns is really just another way of describing things that any seasoned developer has been doing for a long time, and yet they're presented like they're the new holy grail that's going to change everything.

Same with refactoring. Refactoring is just cleaning up code. But the guy who gave it a name is suddenly a genius.

If you drank the patterns kool-aid and you need to talk to one of us old school developers who doesn't get it, try using different words. Instead of a facade, call it an abstraction layer. Instead of a mediator, talk about having some code in between the two objects. We're more likely to understand what you're saying.