BestOfLemmy

I agree. Quality is everyone's job. "QA" as a synonym for "the people that make sure things don't break" doesn't actually prioritize quality as an inherent attribute of the product.

Developers need to write tests and build automatic testing harnesses so they can effectively own the code they write and guarantee its quality. A subset of developers might be "QA platform developer" or something similar, but this is to build tooling for testing, not the actual tests themselves.

Designers can't produce turd of a design and pass the buck. E.g., "That wasn't the intention of the original design." and similar terrible defenses. They have to be responsible for the design all the way through to deployment, not just when they call the design spec "complete". They also need to take feedback from the other groups they work with, instead of thinking their design is above criticism from the non-designer plebs.

Project managers must to prioritize quality initiatives within the project, instead of just driving at feature work or begrudgingly prioritizing critical bug fixes. This includes things like improving developers' and sysadmins' lives through tooling and observability. That pile of tech debt the developers and sysadmins has been talking/yelling/screaming about for months/years will eventually fall over and kill everyone, metaphorically of course... unless you work in a safety-critical industry, like medical or transportation.

Sysadmins (and other operator roles, like SRE) have to be empowered to tell everyone else to pound sand when a new proposed deployment is broken or under-tested, or when deployments have been too broken unexpectedly recently.