DRY requires some judgment If you have two features that have N parts in common, and you are certain that they will never diverge for feature-specific customiz

DRY requires some judgment If you have two features that have N parts in common, and you are certain that they will never diverge for feature-specific customization or special cases, then DRY is probably a good idea If they may diverge at some point, then structuring the code in anticipation of that divergence is a good idea, else you end up with a messy DRY implementation that inevitably has to fork