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.
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|1 year ago
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|1 year ago
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.