3 ms·
>sounds a lot more like a motivation problem than a competence problem. This has been my experience for the vast majority of cases when I worked in software qu
by bumby 6y ago
>sounds a lot more like a motivation problem than a competence problem.
This has been my experience for the vast majority of cases when I worked in software quality. I think the Dunning-Kruger effect may be real, but possibly a special case describing a much smaller subset.
I've worked for orgs where software was an enabling product and not the product given to their customers. The leaders took the perspective that they "do not need world-class ingredients to make a world-class product". Meaning, the software didn't have to great for them to create a great end-product. So it's little wonder why there was little motivation to improve software quality. I think if properly motivated the competence would follow.
>I can say that a not-insignificant amount of projects in corporate America (and probably other countries too, I just have not worked outside of the US) really are "busy work", that create little or no actual value
You may be interested in the book Bullshit Jobs by the late David Graeber
- tombert 6y ago"Bullshit Jobs" has been on my reading list for a couple years now. Maybe I'll bump it up and try reading it soon.