News for hackers. Stuff that matters.
Re:The shittiest project I ever worked on (2013) by org3432 on Friday May 24, 2019 @12:08PM (#20002956)
> But of course, "doing things the right way" is terribly hard to quantify

I don’t think it is hard to quantify actually, shorter build times are better than longer ones, branch merges that take seconds are better than the ones that take up to a day, spending people’s time on higher level thought processes vs squandering their time going through pages of manual steps that could just be a script, etc. It’s just a lack of awareness of what the company is doing that turns them into molasses, and puts projects at risk of being canceled. The companies are still successful overall somehow, but individual employees learn and grow at a much slower pace than they’re capable of.

Re:The shittiest project I ever worked on (2013) by NikolaNovak on Friday May 24, 2019 @10:15PM (#20006716)
Note that not one item you quantified even remotely relates to any business outcome.
Re:The shittiest project I ever worked on (2013) by blauditore on Tuesday May 28, 2019 @11:17AM (#20030973)
Those are not quantifications, just binary comparisons. You could also argue that new Ferraris are better than second-hand VW Polos, but should the company really use them as company cars? The question is whether the benefits are worth the additional cost, and that's where quantification (actual numbers) helps.