That is true, but this is not case in the example. DRY is often a good choice, but you can also use it to make logic shared that very likely never should have

That is true, but this is not case in the example. DRY is often a good choice, but you can also use it to make logic shared that very likely never should have been shared. Untying that knot later on can become very hard compared to code where someone just had repeated themselves. So no DRY is better than wrong DRY, but well applied DRY is of course better still (depending an what we are optimizing for).