[ameminator]

> They are also less productive when coding than the scientists because they care too much about the quality of their work and not enough about getting shit done.

You can't solve the first 3 issues without having people who care about software quality. People not caring about the quality of the software is what caused those initial 3 problems in the first place.

[jampekka]

And you can't fix any of this as long as "software quality" (the "best practices") means byzantine enterprise architecture mammoths that don't even actually fix any of the quality issues.

[ameminator]

There are crazy over-engineered solutions with strict requirements and insane dependency management with terrible trade-offs and compromises. I've worked in the aerospace field before, so I've seen how terrible this can be. It's also possible to have unit tests, have a design and have documentation without the above and would go a long way to solve the original 3 issues.

[hkon]

Yeah, if only scientists would put the same care into the quality of their science...

[aleph_minus_one]

> Yeah, if only scientists would put the same care into the quality of their science...

I guess we see survivorship bias here: the people who deeply care about the quality of their science instead of bulk producing papers are weeded out from their scientific jobs ... :-( Publish or perish.