Unfortunately, "Cultural Engineer" as a title has some pretty scary implications. So the DevOps Engineer is becoming a cultural engineer of the company with a better name.
Which of course is title inflation and title overloading. Now if they'd just overload the salaries, we'd be set.
I've seen this a few times in the thread and I don't get it. Nobody is saying there is a "Cultural Engineer" role, they are saying that there are operations roles and development roles, and that DevOps is not a role, but a culture where the people in both roles understand, help, and cooperate with each other.
A devops engineer should know how to apply devops to your organization before the other roles have become proficient. It's someone to ask vs. reading the Internet for things that might not apply to you.
You are conflating bad sysadmins with systems administration itself, and blaming bad cultures (typically managment driven) on the employees..
Re:DevOps is a culture, not a role
by SoMuchToGrok on Thursday May 25, 2017 @11:58AM
(#14418099)
This train of thought can be dangerous - especially once your business grows to support more than a handful of customers.
Can you name a profitable organization that has successfully eliminated ops/devops? I've yet to find any example of this.
At a certain level of scale, silos can be a very beneficial thing.
The entire thing was brought in to remove the silos between SysOps and Dev. If you have people in the "DevOps" role, then you've just created a new silo, which means you just have traditional SysOps with a new and fashionable, but less meaningful name.