Nice list on the google testing blog on how to write 3v1l untestable code; a list of don'ts, most of which I agree with.

The one I don't is the no-utility-class rule, which doesn't hold in a framework (Java?) that doesn't let you patch in new methods into existing classes.