Skip to content

Repeat yourself, dammit!

Dry is dead and we Killed it.

metru
Apr 5, 20241 min read

Dry is Dead and we Killed it.

top using DRY or making everything into a component/function. DRY leads to complexity. Sure, there might be less of it, but theres a higher density of complexity. I'd rather have more code, that is simple.

One of my favorite scenarios: having like 3 different wrappers of 1 tool. What if instead we didn't write a wrapper and just used the tool raw? Thats way less code, and way less complex since we didn't have to constantly add features to the wrapper to re-expose features of the original tool. And if we need to know how to use the tool, you've got plenty of examples of that vs one really convoluted and generic-ified usage of it.

We should instead use WET(write everything twice/thrice) or AHA(avoid hasty abstractions). Another way to put it is:

Optimize for change first.


What other people say

Other people have said this before and likely did a better job.

Did you enjoy this article?

Recommend it — Standard Reader surfaces well-loved writing to more readers across the network.

Across the AtmosphereDiscussions