No separate job title, though. But similar things are happening in e.g. architecture and fields like mechanical and civil engineering. Used to be that you would have separate draftsman but nowadays you could say “an architect is a draftsman” and it would be about as accurate as saying “a software engineer is a programmer”.
For my money, the crux of DevOps isn't specifically about who does what task with code, it's about vertical alignment. The notion that your build pipeline and infrastructure are as much a part of product development as the coding, design and everything else and everyone up and down the stack is aligned to the same goals.
Whatever your conceit, that's in fact what the term means in practice.
That was one reason that Perl became so popular among sysadmin back in the early 90's: it was a really useful language in which you could do much the same as you could with (and had a syntax which was similar to) shell scripting, sed, and awk, which were tools that were popular among sysadmins up 'till then.
Programming is a subset of skills within the sysadmin role.
You'd be surprised. A large chunk (say, more than 50%) of the sysadmin job market are guys that can set up a Windows LDAP and/or some Cisco and Wi-Fi equipment, but no more.
It's why the 'DevOps' moniker was invented, to differentiate the old-school Unix sysadmins from the LDAP-and-Exchange guys.
It's bridging the gap between software developers and sysadmins where devops falls into place. Taking applications and optimizing their environments, rollouts, versioning, reliability of deployments, reduction of downtime, automating server provisioning, etc.
IMO the best devops are software devs with some sysadmin experience.
To me DevOps: One must understand the build system, stack, and the minutiae related to maintaining that build stream. It's a lot of work and at least in the past was more of a developer responsibility and not a "System Admin" type responsibility.
System Administration: Security, User Accounts, Policy, Backups, Network Configuration, Automation, Reliability.
Sure there is some overlap but these used to be completely separate functions and with good reason there was a lot to understand about each workflow.
Modern workflows (K8s, AWS, Docker, VMs, Jenkins, CI, TDD) have mostly take the "System" out of system administration while improving reliability and speeding development while (I think) suffering security. But that's another post or maybe I will write an article about it.
Its not like they ran the backups at midnight manually.
One type writes a script to back up systems. Depending on their level of expertise they may also include error checking and tie it into the monitoring/alerting system so we know when the backups don't run correctly.
Another type buys backup software, and configures it to back up their systems.
Each type has pros and cons, and each may feel superior to the other. However the ones who haven't coded may find themselves ill-suited to moving to a job where they are expected to be more of the first type, the coding sysadmin.
When interviewing prospective sysadmins, I've tried to tease out whether they are a "maker" or "doer" type of person. The makers tend to be more scarce, and the doers may be ignorant of how much they could be learning and experiencing if they widened their horizons a little.
It may sound like I'm very dismissive of the doers. I'm not, a good team is going to have a mix and have different levels of expertise too.
Sorry despite what IT Managers and HR would like to believe, DevOps is not a role at all, it is a management style.
DevOps is an Organizational Structure, no one should be a "DevOps Engineer" or anything like it.
DevOps teams can have SysAdmins.
The word “irregardless” also got misused long enough that it became acceptable.
irregardless irregardless /ˌɪrɪˈɡɑːdləs / ▸ adverb non-standard regardless: the photographer always says, irregardless of how his subjects are feeling, ‘Smile!’ irregardless, the song is a fine piece of work. – ORIGIN mid 19th century : probably a blend of irrespective and regardless. Irregardless means the same as regardless, but the negative prefix ir- merely duplicates the suffix -less, and is unnecessary. The word dates back to the 19th century, but is regarded as incorrect in standard English.
Why not? What should you call someone who spends most of their time writing code to do with CI/CD, infrastructure provisioning, logging/alerting etc.?
Most sysadmins focus on keeping things running. They are usually taxed to the point that they don't have the luxury of sitting around and writing code to be more efficient.
System Administrator
Systems Engineer
SRE (Site Reliability Engineer)
Just to name a few,
I'm the 'not feature code' director at a company that manufactures companies. Meaning 20% of my time is what you describe above.
This is along side security work, occasionally feature code for one aspect of our moonshot that I have more experience than everyone else on, architecture work for all the properties to make sure they can talk to each other (while still maintaining enough separation that we could sell any of them at any time), building out a small manufacturing facility, and managing their transition to docker (which they only pursued because I pushed it). I also manage 2 other people (one of whom is a remote contractor) who do bits and pieces of the same and yes, a little endpoint laptop crap.
If they had billed the position as a sysadmin I wouldn't have taken it. Sysadmin pigeonholes you into a very specific role in many peoples eyes, whether it's true or not. Labels matter.
(In fairness, I think Google brought this on themselves by reusing SRE as both the job title and the philosophy.)
I was hired as a dual Sysad/developer years ago as an explicit DevOps role (before devops was a thing)
The team (telecoms billing systems) was also uncertain that the actual ops team could provide the required service.
Its not enough to just rename your IT guys devops. However, When you're a stickler about titles its also counterproductive to the goal of removing the wall between dev and ops.
If you're working with Linux systems and automating stuff, make yourself a favor and call yourself a DevOps.
Whether you want it or not, sysadmin is left to designate the low end of the market, namely desktops and windows administration work, sometimes all the way to helpesk. Devops simply evolved as a separate term to designate the higher end of the market around linux and automation.
Maybe in the silicon valley every company is a tech company looking for linux sysadmins and developers, but in the rest of the world "sysadmin" will usually get one into windows or low end roles.
No, sorry. They were sysadmins. DevOps is valuable role, and I'm glad there's a focus on supporting developers and their needs, and in empowering developers to manage their own build and deployment infrastructure. In a larger organization, having a dedicated person or team working closely with developers on software build, test, and deployment automation is great.
But if your job is maintaining production hardware, network, operating system, DNS, SSL certificates, firewalls, backups, etc., then you're a sysadmin. It's not a pejorative term. In a small organization, or within a team, that may be combined with a DevOps role. You may even have one person who maintains all your infrastructure for production and development, and even doubles as a developer. That still doesn't mean you label the entire role DevOps.