Re:Is High Quality Software Worth the Cost?
by BeetleB on Thursday May 30, 2019 @10:40AM
(#20051622)
>Most of the time when a team is writing low quality software it's not really a choice. No one made a conscious decision not to write tests, not to do PR reviews, or not to refactor.
And then:
>That is a much bigger and much more time-consuming problem.
Right there is the choice.
Most comments here are blaming management. I've worked in a team where the team themselves were the ones opposing it. Yes, like you said, they worked for years without doing all this. But then management actually gave them leeway to spend time learning it and implementing it - on the job, but it was left to the developers to figure out how to learn it. They could learn it solo or form learning sessions - whatever they wanted.
Only a few developers took advantage of the opportunity. And the rest who hadn't then actively opposed changing the code for testing.
People generally don't want to change. In this case, it definitely was a choice.
And then:
>That is a much bigger and much more time-consuming problem.
Right there is the choice.
Most comments here are blaming management. I've worked in a team where the team themselves were the ones opposing it. Yes, like you said, they worked for years without doing all this. But then management actually gave them leeway to spend time learning it and implementing it - on the job, but it was left to the developers to figure out how to learn it. They could learn it solo or form learning sessions - whatever they wanted.
Only a few developers took advantage of the opportunity. And the rest who hadn't then actively opposed changing the code for testing.
People generally don't want to change. In this case, it definitely was a choice.