[lmorchard]

Yeah, that sounds like fundamental team dysfunction that no amount of engineering tooling or gatekeeping will address in any positive way.

[sublinear]

Even the best management and company culture cannot change that. In engineering terms, these "dysfunctions" are analogous to impedance mismatch.

Hire people who actually know what they're doing and only keep them for as long as they will work as hard as your devs. If they start burning out and shoveling their work onto devs you must protect your dev team. Let's not forget that non-devs are supporting staff. They're not essential and you're better off without them and their incompetence. Even the tiniest slack from them will be highly disruptive as errors accumulate and waste lots of time. Why not just make cuts and save your payroll while you're at it? If you have doubts look at any startup. A skeleton crew looks like almost all devs.

[couchand]

I have to say, this is an incredibly arrogant and unhealthy attitude. Based on your comments here it sounds like you might actually be the main problem at your organization.

I would recommend spending some time reflecting on your ability to form relationships with others and try to come to see the contributions that all the members of your organization can make.

[sublinear]

> your ability to form relationships with others

Not sure where you're getting this from. I have worked with both competent and incompetent people regardless of their role.

The relationships between coworkers are built on their competence, not their personalities. Professionals focus on the work not self-expression. The most competent people I've worked with have always been straightforward and neutral in temperament and that's all anyone should expect.