DRY has become a mantra throughout the industry. Any time repetitive code shows up, DRY gets applied as a cure all. If you even start to question DRYing up a piece of code, you are viewed as a heretic to the entire industry.
Ok, maybe it’s not that bad, but many times DRY gets applied without much thought. This careless application of DRY leads to brittle code, making even simple changes scary because they could have a huge ripple effect.
Yeah, this definitely went deeper. I was really tempted to change the title to be honest. The article started out of a frustration of a code base that was too DRY, and kind of grew into a more general how to create abstractions. The original title just stuck around.
That absolutely makes sense, still thoroughly enjoyed the article!
Something else interesting to think on, is which terminology helps the average programmer more. If DRY causes habits to form around human/business terminology maybe it should be avoided in favor of abstraction layers! No idea what the answer is in this regard, fully possible theres no difference. But its an interesting thought experiment all the same.