For me it's all my own fault or lack of resources in other departments. For instance if I work on legacy code that is real janky I have two options: add more jank, or rewrite it to follow at least some general good practices. All changes like that require something like 4-8 jira tickets, many hours of approval meetings, and time in the QA department. So most of the time I pick more jank xD. If the code is somewhat self contained I can get away with rewriting it to modern standards. New code I am much more strict with code quality.
And everyone has their own opinions on "good" code but I can say there are a few well accepted things. Code with tests > code without. Separation of concerns > one giant function. Variables that describe purpose > x, b, g.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.