To talk about “duplication is cheaper than the wrong abstraction” without invoking "dependencies" at all (and their costs) means the entire premise has been mis

To talk about “duplication is cheaper than the wrong abstraction” without invoking "dependencies" at all (and their costs) means the entire premise has been missed. Another tell: > Don’t try to make one thing act like two things. Instead, separate it into two things. If abstractions were so easily split like this, then the advice wouldn't hold. But they never are. Abstractions immediately accumulate dependencies making it near impossible to split them, as we all learn after living in anything other than toy code bases. This is the hallmark of a junior (ie someone who has not been to battle much) is making de-duplicating code a priority and not understanding the cost of dependencies.