This isn't about devs versus ops. It's about bureaucracy versus getting shit done. If it takes 3 weeks to ensure reliable infrastructure and backup, I wouldn't complain.
All I was saying is that if you have to wait 3 weeks for the simplest schema change request (which I saw it happens in big corporations), then you should take charge and workaround it before throwing your hands in the air ... sometimes management listens.
This is fine as long as you actually understand what it is you're working around, why it's there, and what the consequences are of working around it. What looks like bureaucracy to a technologist may well be there for a very good business reason.
Sometimes there's a tree across the road simply because a tree fell across the road. But other times there's a tree across the road to keep you from plummeting into the ravine where the washed-out bridge used to be.
Oh yeah, if it's broken, fix it, I don't meant tech but organisationally. Just pointing out that there's often more work that goes into databases than endusers see.
All I was saying is that if you have to wait 3 weeks for the simplest schema change request (which I saw it happens in big corporations), then you should take charge and workaround it before throwing your hands in the air ... sometimes management listens.