Programming

It's really about making a conscious choice about which part of your application to keep "humid". Because you will have repetition somewhere no matter how good your abstractions are. I am advocating for a "humid" top layer and DRY lower levels.

The approach I see too often with overuse of DRY is creating a lot of small functions that only slightly differ in the steps they take. Then you end up searing through those functions, creating new ones, creating duplicates, or using the wrong one. I think it's easier to maintain a well named, straightforward list of steps.