How is a sysadmin different from devops?

Question

System administration

Hello. I looked at the vacancies: the system administrator receives n rubles, and the system administrator and devops in brackets receive 1.5n or even 2n rubles. What's the difference?

Answer 1

Compare the list of requirements and see how they differ

Answer 2

Just different professions. Albeit related.
Different knowledge, skills and tools.
From the fact that you are a good system administrator, you will not be able to immediately become a devops. Need to study again.
These are essentially different professions.
Typical difference: the programmer gives the system administrator a code. He raises MySQL, nginx, php. Sets up this economy and sets the programmer on the code.
Ops writes Ansible guidelines that do the above.
DevOps set up Kubernetes and GoCD, etc., so that the programmer sends the code to git, and then it starts testing and deploying itself. The
key feature of DevOps is automated CI / CD. Automated to the max

Answer 3

Almost nothing in today's world.

Answer 4

InoMono answers the closest, but I advise everyone to delve into the comment thread, since the original answer is very muddy, and there are normal and intelligible explanations from him in the comments.
The answer to the question of the TC, in short: what is written in the vacancies of "devops engineer" and other "devops is another word" in fact - only the wishes of a particular company for organizing devops processes. For example, they need someone who will set up the already mentioned ci \ cd and, most importantly for business, will reduce the time to roll out the code to live to a minimum, removing, among other things, a bunch of manual labor (which is a waste of time, and therefore money).
What is the difference, respectively, with the system administrator?
Sysadmin is an explicit opsand is not required by default to handle code delivery processes.
You can work in a small factory, have your own server room with a set of servers, deal with external mail, web servers, IP telephony on asterisk and a bunch of obviously ops activities, and not be related to the delivery of any code, since you only have one kind of programmer - 1s-nickname. It may well be that this programmer is also you :D
You can deploy web servers with all the adjoining ones in a small web studio, and also be only a sysadmin. But here you will soon die out, you are not needed here: as soon as there is a need to deliver the code (especially if it is written by more than one person), then it becomes necessary to establish processes from devops practices.
PS no one is stopping you from using Infrastructure as a code practices and others from devops and generally raising the entire infrastructure with a terraform. Nobody prevents you from setting up servers with the help of chef\puppet\ansible, being a system administrator is your plus, your step towards the complete automation of your work. Devops, however, you still won't build in your factory.