4 ms·
"Why do it right when you can do it twice." is one of my favorite lines to developers who insist on going fast.
by onion2k 5y ago
"Why do it right when you can do it twice." is one of my favorite lines to developers who insist on going fast.
- marcosdumay 5y agoDoing it right takes too much time. It's better to do it twice and have your clients give up and throw it away because they can't use either result.
- forgotmypw17 5y agoI think there's something to be said for doing it twice, or several more times. I've read many well-accomplshed devs say that they don't get it figured out until several prototypes in, and a "good" version doesn't come until the seventh rewrite.
- onion2k 5y agoIterating to a correct solution to a problem works well as a strategy for projects, but very poorly for smaller units of work like a feature or a bug fix. Often, doing the quick hacky solution for a feature won't show the problems it has for a while, by which time you've built things on top of it. Having to go back and fix that impacts far more than if you'd spent a little more time in the first place. It's particularly important when you're designing data structure changes more than than code. Getting an API or a database table design right first time (or even just 'more right') is worth the time invested.