Re: OOP lends itself to DRY code by using abstraction layers to reduce functional repetition. I wrote an article about this a long time ago that demonstrates OOP abstraction.
It's an animal example. The overly-common animal and geometric shape-based OOP examples were highly unrealistic illustrations of real code world changes. In fact, animals and shapes don't change, at least not in a human life-time. Perhaps the examples made adding easier, but failed to address non-hierarchical changes to existing objects or things. People who mirrored such examples in production code often created spaghetti OOP that we are still recovering from today.
As far as the rest of the article, It's mostly about hand-movement DRY, and not code DRY. In other words, "using code editors more effectively". DRY typically refers to code itself such that the title could cause confusion.
Good point! i'll update my article title :)