I 100% agree that DRY code is better than WET code, but I do voice one word of caution. While DRY code is easier to maintain in the log run, if you are not careful about how you break your code up to account for DRY, you can run into what I refer to as the `Java Factory Syndrom`. There may be another name to it, but I have seen Java projects become so obtuse that they start to become unmaintainable due to being overly engineered in an effort to follow a standard. As a result, you start to loose out on the benefits that DRY code actually give you.