3 ms·
well i think this is certainly the problem--ie, now "garbage" looks justified but those aren't really the two alternatives, are they--ie, crap code or nothing?
by doug1001 9y ago
well i think this is certainly the problem--ie, now "garbage" looks justified
but those aren't really the two alternatives, are they--ie, crap code or nothing?
it might be in the very short terim (ie, by this friday)
but over any other span of time, the choice is more like:
ship crap code in 30 day, followed by 50% of the team's resources spent bug fixing (which can often be cleverly disguised as new features) for the next 90 days
OR
ship high quality code in 45 days
- megaman22 9y agoSadly, it's hard to convince people that doing things right is better than doing them wrong, but quicker. That customer needs this code on the 1st, that is a hard and fast deadline! So shit is churned out, and handed over on the 1st. Then, three or four 1sts later, the customer finally gets their shit together and deploys it, and, voila, it is shit. And the cycle continues, as the scramble ensues to patch the shit by the 15th with yet more shit. And you end up like the little Dutch boy at the dike, except instead of fingers you're using hotfixes made of excrement.