I think devs in general sweat too much about code quality.
I think devs in general sweat too much about code quality.
There's not really a book or standard on opinionated code quality that satisfies a majority of the people in the field. There's way too many ways to build things for that to exist.
This leaves it up to individual teams to approach a shared consensus (with some wiggle room) within their domain and tool set.
One thing that is universal is how strict the enforcement of a team's quality standards. So as a developer, you have to decide whether you like strict or lax enforcement of quality standards. Everyone can decide that but I think most don't.
We have code like that, and it requires everything around it to twist and contort to comply with the beast of unmaintainable at the center of it all, simply because at this point it has so poor test coverage and is so incredibly mission critical now.
I think if they sweated a little more then poor quality code wouldn't find itself into the codebase.
But almost all PRs I review have something in them that suggests the developer not putting as much thought/care into what they were doing as I'd like to see (and I'm just as capable of doing the same).