This is a great showcase of the silo mentality and split.
One should not build silos where experts sit.
One should participate in a team of many different experts.
If you still have to call "whatever department" for fixing your slow SQL query, your disk space, your repo access, production deployments etc. Then in most cases I feel you should get out and find a place where silos are not being exercised.
Is it? In highly regulated environments, silos are practically a requirement. Security access controls are intentionally put in place to limit access to systems and their respective pieces. If you need repo access, or access to the CI pipeline, or access to the database, you have to go to the appropriate channel.
The scale of security necessities in organizations runs from:
- no need for anything but minimal security, perhaps because the business is trying to surf the margin between their AWS bill and their Google ad revenue.
- there is only a need for security in the part of the business that deals with money
- some stuff that the users do, they would prefer to maintain integrity but they don't care a lot about confidentiality
- the users want reasonable confidentiality, too
- everything about the business is money or secrets
Where your business is on that scale determines how much you are regulated and how many internal gatekeepers are necessary.
One should not build silos where experts sit.
One should participate in a team of many different experts.
If you still have to call "whatever department" for fixing your slow SQL query, your disk space, your repo access, production deployments etc. Then in most cases I feel you should get out and find a place where silos are not being exercised.
This is a thing of the past.