Re: The problem with DevOps . . .
It is also my experience that Dev's in general are terrible at dealing with Op's. They cannot comprehend, or probably don't care, that you cannot just treat an OS and hardware as throw away items without consequences. Or that changing it in favour of 'your current favourite thing' can massively impact other 'things' sharing the resource, or even break the OS and/or hardware itself. They're not even slightly interested in doing configuration or fixes at 3am on a Sunday morning. Many think they're entitled to their very own instance of a VM to do what they like. They'll get in there an tweak everything they can to the point it looks nothing like where the application will eventually be deployed and then wonder why it fails at implementation or causes wider problems. They'll usually blame it on Op's in this case.
Most Op's people I have known over the last 40yrs are not really interested in trying to force change on Dev's other than reminding them of common sense things like efficient use of storage for example. And generally Op's are always accommodating Dev's as much as possible, juggling the competing team requirements while being kicked from all sides. They will have some red lines though, particularly in production, and this is the thing Dev's cannot abide, they'll flail about trying anything to be the 'special exception'. But Op's know that exception would break something, and they know they will be blamed for it. Op's are stuck with this common piece of the puzzle, the OS's and hardware that ALL the applications run on. They cannot just say I've finished with this application and move on like Dev's. They support all the users day in day out and have a much wider view of how all the workloads affect the operations.