The crux of the argument is: > I think “the wrong abstraction” is a confused way of referring to poorly-de-duplicated code. But I believe this is similar to a

The crux of the argument is: > I think “the wrong abstraction” is a confused way of referring to poorly-de-duplicated code. But I believe this is similar to a no true Scotsman fallacy. “If you just make the right abstraction, de-duplicating is fine!” Yes, if you’re good at making the right abstraction, it’s not worse! Those are the cases when I definitely do the refactoring: when I know for sure I know the right abstraction. Otherwise, I defer the decision for an older, smarter, wiser me (or future maintainer).