The problem with DRY is that the cost of it being wrong in the future often isn’t accounted for.
Copy, paste, search, replace is underrated.
That said, it’s a balancing act. The right generalisations are great.
Probably people just call it 'Refactor'.
The requirement changes and you refactor it to meet requirement.
And that's all you need to do to avoid premature generalisation.
