That's a good sign you're doing it right. When you get more out of less code after you refactor. If you're refactoring and you get more code and it all does the

That's a good sign you're doing it right. When you get more out of less code after you refactor. If you're refactoring and you get more code and it all does the same thing, well not so good an idea usually. One of my ongoing frustrations with java is that it is almost impossible to make less code. Short of a fixing a poor algorithm implementation, most any reworking in java just ends up with another heap of code. Reminds me of this: http://steve-yegge.blogspot.com/2007/12/codes-worst-enemy.html http://steve-yegge.blogspot.com/2007/12/codes-worst-enemy.ht... Java programmers often wonder why Martin Fowler "left" Java to go to Ruby. Although I don't know Martin, I think it's safe to speculate that "something bad" happened to him while using Java. Amusingly (for everyone except perhaps Martin himself), I think that his "something bad" may well have been the act of creating the book Refactoring, which showed Java programmers how to make their closets bigger and more organized, while showing Martin that he really wanted more stuff in a nice, comfortable, closet-sized closet.