title: Any suggestions for a crash course on design patterns?
body: <p>I am going to be giving developers at my company a crash course on design patterns (after coming across some scary code recently).</p>
  
  <p>One of the most important things I want to put across is that they save time in both the long and short term (which they really do!) - as developers here are put under quite a bit of time strain. All in all I need to demonstrate the every day benefits - things that will let them go home early.</p>
  
  <p>Telling them that it might mean less bugs probably isn't going to hit home. I need stuff that is going to sink in.</p>
  
  <p>I will probably do three to four sessions of an hour each. Do you guys have any suggestions on what to touch on/to do?</p>