2 ms·
It's a cost benefit tradeoff, but I still think far, far more people routinely underestimate the costs and overestimate the benefits than the other way around.
by jerf 16y ago
It's a cost benefit tradeoff, but I still think far, far more people routinely underestimate the costs and overestimate the benefits than the other way around. In all the major systems I've worked on in the past five or six years, I've always gotten serious leverage making sure I'm working DRY, and thus able to do more with less, and in particular these past three years have A: involved me doing a project where if I had adopted this mindset it would have failed in the worst way possible, initial modest success followed by endless soul-sucking failure brought on by code debt brought on by DRY violations, and B: having the worst part of my day-to-day coding (and, correspondingly, the most expensive part for my employer) being the part where I have to deal with a large mass of non-DRY code. In fact my current project is basically replacing a clusterfuck brought on by a system that adopted the recommended approach quite extensively.
In my admittedly limited experience, non-DRY code still has huge costs that are easy to gloss over at first and a benefit curve that curves down way faster than anyone would like to admit. In many cases people can't even see how fast the curve is trending down because they've never even seen a properly-done product.... and I don't even mean "a product done to the pitch of academic perfection", I just mean a decently done product that isn't perfect, but we still put significant time into staying DRY and fixing DRY violations.
YMMV, of course. I suppose ultimately people following this advice has certainly advanced my career, as I clean up behind them...