DRY is about code you write, not the code artifacts you ship to the client.

Thank you, that is a really good distinction.

When DRY makes you commit to bad abstractions, it's a harmful practice.

Where I work people have been trained on not over applying DRY. Which o actually agree with but some people take that way too far and duplicate needlessly in favour of even the simplest abstraction.. a named function. I am scarred by that

Yes?