I don’t know. As someone who has tried to introduce the simple concept of version control to various sysadmin orgs over the years, I am fine with many of those types of sysadmins going away
A lot of those guys just couldn’t handle a reality where they couldn’t name all their systems with cute Dr Who hostnames and do all their work as local root with riced out bash prompts
Devops at least forced them to the same table with the dev org, and if they ended up getting replaced in the transition then I shed zero tears
I introduced RCS to my sysadmin team in the mid 90s but again you always had those guys with god complexes who couldn’t be bothered to ‘ci -u’ or ‘co -l’ properly because that’s not how they do things. And if your entire team isn’t onboard then it’s worse than having no VCS at all
God riddance to those guys. They thrived in silos.
Well, some people are not agreeable, do not want to be seen taking guidance from others.
They are not worried about understanding what they do, or improving their practices, they are worried about status and how others perceive them.
Those people may be able to protect their status in the short term, maybe even bluff and be promoted. But they will never truly understand what's going on.
A lot of those guys just couldn’t handle a reality where they couldn’t name all their systems with cute Dr Who hostnames and do all their work as local root with riced out bash prompts
Devops at least forced them to the same table with the dev org, and if they ended up getting replaced in the transition then I shed zero tears