3 ms·
To me, you're just describing another layer of management. Which is fine--management is important!--but it's not the same thing as the actual implementor class
by eropple 10y ago
To me, you're just describing another layer of management. Which is fine--management is important!--but it's not the same thing as the actual implementor class that "sysadmin" usually refers to. And those people are inexorably going to be doing their administration via code. There isn't enough time in the day to waste with "pet" servers. They're cattle. Infrastructure as code is here, and it's just going to grow more extensive. If you can't write code effectively--both in terms of stuff like "hey, this code can be read by other people" and "this code can be automatically tested like any other code"--you're in trouble. One of my clients is a top-10 commercial bank in the United States that has not only moved entirely into the cloud (save for some legacy mainframe stuff that they're working on) and every team is not only required to provision and operate strictly with automated tools (both instance and cloud-level provisioners), but their non-database servers are killed automatically every few months to ensure that they're rotating successfully and without human involvement.
I'm pretty confident that I've seen where we're going with this. The management piece of the puzzle is totally important...but the practice is going to continue converging with every other bit of software development.