If you don't understand that development, security, and operations are all one job you will constantly make crap and probably point at some other team to make excuses about it, but it will be actually be your fault.

Programs have to run. They have to be able to change to meet needs. Implementing working security measures is one of those needs.

The amount of times I've had to slap devs hands that wanted to just disable security or remind security that just shutting it down is denial of service is crazy. If it can't deploy or is constantly down or uses stupid amount of resources it's also worthless no matter what it looked like for split second you ran on on the dev machine.

The next patch isn't going to fucking fix it if no one that writes patches knows about the damn issue. Work arounds are hidden technical debt and you have to assume that they will fucking break on some update later. If you are not updating because it breaks your unreported workarounds you will get ignored by the devs at some point, and they are right in doing so.

If you depend on something communicate with the team that works on it. We can send a fucking petabyte of info around the world and to the moon and back before some people write a fucking Ticket, email, or even a IM. Look dumb and asking the stupid question rather than being an actual idiot and leaving something broken for the next decade. We're all dumb, it's why we built computers, get over it and just talk to people. If you really struggle with, don't just communicate, try to over communicate, say an obvious thing now and again just to keep the dialogue open and test that you really on the same page.

That's my rant/hill borne from ulcers supporting crappy IT orgs and having to overcome my own shortcomings to actually say something in channels where things can actually change and not just griping in private about it.