That gets to where I said management needs to give not only permission, but direction. Most developers have no clue about operational needs, and don't really wa

That gets to where I said management needs to give not only permission, but direction. Most developers have no clue about operational needs, and don't really want one, and they can be very resistance. And vice versa for ops staff. So it's not enough for management to just get out of the way - there will be some pushing to do, and lots of Corncob antipattern issues. I've spent most of my career as what a colleague called a "one man devops team", basically serving as a sympathetic liaison to both sides. The root cause of the problem is organizational walls between dev and ops, but the industry-wide result is a sort of mutual distrust and even contempt.