I believe there is something missing from this article. To me it's not only about specific skills which the author ties directly to particular tools and langua

I believe there is something missing from this article. To me it's not only about specific skills which the author ties directly to particular tools and languages, but at least as much about ideology and methodology. For example, I entered the tech world in the early 1990s, and shortly found myself specializing as a 'Unix Systems Administrator'[1], meaning one who was well versed in Unix OSs, related things such as shell scripting, Perl, and core infrastructure stuff like DNS, SMTP, NNTP, etc. Back then this was enough to be considered a full job spec and career. Now it's simply the expected the price of admission for a variety of roles, and trying to find a pure old-school Systems Admin position is practically impossible; the skill set in isolation is no longer marketable. However, this skill set is the basis of a lot of types of work, including the modern DevOps ideology. In DevOps you add a few tools, learn about real big data, configuration management, and maybe adopt a few more powerful languages to take you beyond good ol' shell. It's not the tools that separate DevOps from Systems Admin work, it's the philosophy and approach. Those original SysAdmin foundations are at the core of any DevOps engineer. The tools are not radically different, it's the crucial paradigm difference that actually matters. I'd agree with the basic premise of the author, but I'd add that it's as much about keeping up with evolved methodologies that's as important. [1] Grandiose title deliberately icky!