<a href=http://weblogs.cerkit.com/mearls/>Michael Earls</a> has a post about a co-worker who <a href=http://weblogs.cerkit.com/mearls/archive/2004/12/10/526.aspx>doesn't do patterns</a>. <p> I can understand both sides of the argument here. <p> 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.<p> Same with refactoring. Refactoring is just cleaning up code. But the guy who gave it a name is suddenly a genius.<p> 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 <a href=http://c2.com/cgi/wiki?FacadePattern>facade</a>, call it an abstraction layer. Instead of a <a href=http://c2.com/cgi/wiki?MediatorPattern>mediator</a>, talk about having some code in between the two objects. We're more likely to understand what you're saying.<p> Thu, 01 Sep 2005 19:17:07 GMT