I used to play a particular game of code golf with my co-workers. Basically write the most awful code you could. We would usually pick some rule for the start of the game that week to have a theme. Something like 'write a loop that finds a string' or 'make a case statement'. There were no real rules other than every language construct and library is on the table to do it and it had to fit on the whiteboard with everyone else. So for example you may be a C++ shop that avoids throw in all cases that you can. In this game you could use them.

It had a really interesting side effect. The code in the office that was checked in went up dramatically in quality. As we learned first hand what was 'bad code' and why.

We basically forced bad things just to have a bit of fun but accidently learned something while doing it.