I have see a dry bug. It happens when you deduplicate code which isn’t an exact duplicate, but only appears to be.
For instance, one piece of code is supposed to do the same thing as another, but in context it caused a side effect that some other part of the code was inadvertently relying on.
>> It happens when you deduplicate code which isn’t an exact duplicate, but only appears to be.
Embarrassing to admit, but until now I didn't think in this perspective - and on hindsight it should be obvious, sometimes code might look duplicate, but is not
Or worse, the natural progression should be that they diverge, but because they now share some kind of "reused" code in a library or class, an abomination is added to one or both users, just to keep the original "shared" feature.
