DRY skips the part about dependency management: Will tying these parts together make sense for future readability, changability, or not? Often it is wise to be

DRY skips the part about dependency management: Will tying these parts together make sense for future readability, changability, or not? Often it is wise to be clear what and how to separate and encapsulate. If there is only one right way, there is no reason for change or changing together, so is not shared knowledge.