Re:It Takes 6 Days to Change 1 Line of Code (2015)
by ubernostrum on Tuesday December 06, 2016 @06:48PM
(#13119290)
Yeah, this is the kind of "everybody's empowered to push back and insist on doing things correctly" environment that people normally praise. Or at least, they praise until they realize that people will push back and insist on quality, and then they decide it's stifling and prevents them from getting anything done.
[ Parent
| on HN ]
Re:It Takes 6 Days to Change 1 Line of Code (2015)
by omouse on Tuesday December 06, 2016 @07:05PM
(#13119387)
The problem is when the push back is not standardized. I've seen bad code go through with comments like "we can deal with these things in a later PR or two" but then other code gets flagged for "it fixes one problem but it could fix three other things too" which increases scope. An inconsistent standard is better than no standard but it's just as frustrating.
Re:It Takes 6 Days to Change 1 Line of Code (2015)
by user5994461 on Tuesday December 06, 2016 @10:41PM
(#13120295)
They're not pushing on quality. They are plainfully pushing against it and deliberately risking to introduce more bugs.
Re:It Takes 6 Days to Change 1 Line of Code (2015)
by jocro on Tuesday December 06, 2016 @10:27PM
(#13120221)
It's all a balance though, right? And really, about the flexibility of the environment. You have to be able to recognize and deal with a broad spectrum of priorities - this, at least, was not prioritized highly enough across the environment and that meant it wasn't handled gracefully.