I have become fanatical about writing unit tests for every method on every class, regardless of how trivial that method first appears. ( "But it's just a getter!" )
This leads to an interesting laziness driven feedback loop. Here's what happens:
I am implementing a feature, and think that the shortest distance between two points, is to add another dependency onto one of my classes, but then I realize that this new dependency would further complicate all of my tests, requiring large changes. Ugh! I don't have time for sweeping changes to my test suite.
So, in my laziness, I skip over the initial, obvious solution, think a little bit harder, and come up with a truly simpler solution.
