3 ms·
I mean, sure. I'm generally more WET than most of my colleagues, but this... > Applying DRY principles too rigidly leads to premature abstractions that make f
by michaelcampbell 2y ago
I mean, sure. I'm generally more WET than most of my colleagues, but this...
> Applying DRY principles too rigidly leads to premature abstractions that make future changes more complex than necessary.
... is just one of those things that sounds wise, but is just basically a tautology. Use the best tool for the job, etc. No kidding? Would never have thought of that on my own, thanks sensei.
Seriously, the issue with the quoted statement is not that it's new to anyone, it's that no one thinks they ARE applying DRY principles "too rigidly". This is just chin beard stroking advice for "everyone else".
- AnimalMuppet 2y agoWell, then, here's some advice: Learn when to DRY, and when not. No, you probably don't know as well as you think you do. No, you're not going to get there by grinding leetcode. No, you aren't going to get there quickly, or without a lot of interaction with more-experienced peers, or without being told that your judgment is bad a few times. (And if you don't listen - really listen - then you don't learn.) Good judgment in these things takes time and experience. If you have a year of experience and think you know, you're probably wrong.
- protomolecule 2y ago>takes time and experience Or maybe asking yourself what end goal you're trying to achieve by building an abstraction.
- protomolecule 2y ago>it's that no one thinks they ARE applying DRY principles "too rigidly" But they should think twice if they are building abstractions only for the sake of DRY.