It fell to deaf ears that a packaged approach was the right way to go, given said software installed its own jungle all around the filesystem hierarchy, numerous times conflicting with software from other vendors with the same kind of recklessness.
Quite clear that any of these people lacked the understanding that having a longterm stable environment where everyone uses the same version of everything, is uncomparable with doing unsafe installations following the first forum-post you find online.
Devops learned them that cutting corners to empower yourself is OK, they could run their own systems quicker. Needless to say all the debugging (the search-engine based kind) that needed to be done after the facts was suddenly part of their job description, and filled up most of their time...
I get we need to adapt to support devops. I'm investing big resources to support that. It would be so much easier if so many devs didn't think devops == no oversight.
We're looking at deploying some tools (e.g. Dome9) that we think will close some of the loopholes and provide more automation. However, due to the complexity of these environments, I'm not sure there's a perfect solution.
We do, again and again, and from some people we get nothing but condescension in return, and treated like unskilled janitors who only ever stand in the way.
If I had a penny for every stuck up sales/marketing person or exec who though everyone in IT was lower than pond scum...
This condescension even comes from developers, who you'd think would have some sympathy for other tech roles, but the attitude is often that devs are gods compared to the lowly ops guys.
"most sysadmins don't make the money, the people they support do"
This attitude is part of the problem. You don't appreciate that it's a team effort.