Here's an example of a modern mindset with trailing-edge technologies: I'm having to learn VMware for my current job. I had hoped to literally never do so. (I don't want to manage a data center. But if you use certain cloud providers...you manage a tiny data center.) But I am learning and applying VMware through the lens of pervasive automation and systematization of the problems I'm actually trying to solve. While the team in place before me spent most of their time installing minimal automation (configuration, monitoring, etc.) we are making it a prerequisite of our ownership of the infrastructure for this team's product. Because we like to be able to sleep at night.
Understanding how to systematize and automate is a more employable skill than having a very high-level understanding of, say, Active Directory.
I'm a software developer first and foremost. When I've needed to deal with hardware, I learned it. And it was easier because the first question was always "OK, now how do we make this something a human doesn't do?". It's a band-pass filter for what actually matters to continued operations.
I could be confusing this with Dune. [1]
So I get the overall goal here, but reading this, this feels like somebody's trying to fight the last war.
> Since the early 90’s, operations engineers have been in high demand. As a result, these positions often offer high salaries and long term job security.
...because most of the control surfaces offered minimal automation and there were many fewer options for management. This isn't even a "well, AWS/GCP/Azure will eat your lunch" thing, it's a "the robots can do most of this already" thing. There are still roles for network engineers, large-scale datacenter management, and that sort of thing--but this "curriculum" reads as very...hands-on...when a holistic, automation-first approach is overwhelmingly preferred in industry (outside of the trailing edge, where those high salaries and that stability aren't nearly as common).
Again: not saying "use the cloud, datacenters don't matter." But I'm not sure that this encompasses what "ops" typically means (as opposed to "IT", which is itself becoming a largely automatable and automated function, or "devops", which will get there sooner than later) and I'm very unsure that places that will still be dealing with data centers in ten years, instead of outsourcing it, will benefit much from juniors with this skillset instead of one built around software definition and a pervasively automation-first mindset.