Re:Robinhood Is Down Again?
by ndynan on Tuesday March 03, 2020 @10:57AM
(#22475555)
Often it's not dev managers, but a level above who don't prioritize QA engineering because they see it as a cost center and find it difficult to quantify the risk. If it's not leading to growth it is de-prioritized until fires are burning.
[ Parent
| on HN ]
Re:Robinhood Is Down Again?
by saalweachter on Tuesday March 03, 2020 @11:56AM
(#22476249)
A lot of the trouble is that good QA -- and good engineering practices in general -- usually comes down to some equation like velocity x quality = $. If you want to increase your code quality, you either have to slow your velocity or jack up your $'s -- and usually you end up doing some combination of both, going a little bit slower and spending a little bit more money.
And if there's one thing people hate more than going slow it's spending more money.
Re:Robinhood Is Down Again?
by baal80spam on Wednesday March 04, 2020 @01:59AM
(#22481743)
Being a QA guy myself, I am of the opinion that this sums it up pretty well:
Re:Robinhood Is Down Again?
by saalweachter on Wednesday March 04, 2020 @07:36AM
(#22483185)
My reformulation is mostly out of ignorance, but since this is the internet, I will contend in a fit of pique that in modern software development, velocity (which is basically scope / time) is more interesting than the two factors individually, because so many of us live in a nightmare world where there are not finished projects, just continuous iterative release cycles.