this post was submitted on 10 Oct 2023
42 points (76.9% liked)
Programming
17406 readers
105 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What makes DevOps so different from sysadmin? Recruiters always told me "it's nearly the same", but I never got the job, so I guess idk.
It's actually pretty distinct. DevOps refers to the mindset (or philosophy, if you will) of "you build it, you run it". It boils down to you as a software developer are also responsible for packaging up you masterpiece, pushing it through CI, getting it deployed and making sure it keeps on running smoothly. It is designed to shift responsibilities away from the sysadmin to the developer.
The problem with this is that it's not a role or a job title, so recruiters and HR does not know how to work with it. Hence, they invented the DevOps "Role" because it sounds more modern. So in reality its used as a marketing term most of the time. So when someone pitches you a DevOps jobs, this tells you a few things:
Not quite. Basically a DevOps role includes the responsibility of fixing pipelines and be paged in the middle of the night if something bad happens with the app.
Instead of paying a sysadmin and a developer who don't talk to each other, you dump all responsibilities onto someone else and at least eliminate the finger-pointing part between sysadmins and developers when something bad happens.
Recruiters lie my dude.
They are similar but with a strong knowledge set in different tools.
Makes sense I didn't get the job, I only vaguely know the difference and it was mostly theoretical stuff like CI/CD, but those recruiters really wanted to throw me at random interviews to see if I'd stick :D
PS: sorry I offtopic'ed to recruiter-hating, gonna go find a community for that.
You good homie. I shit on recruiters frequently. I have them hitting me up all the time for in person stuff from LinkedIn when it actively says no in person stuff
Usually recruiters know jack shit about what they are recruiting for. Their main responsibility is trying to sell the idea that recruiters play a relevant role in recruiting, when in tech they quickly pass the ball to anyone else to assess hard skills.
The goal of some recruiters is to source candidates and thus line up a list for their paying customer to go through. Their goal is to pretend they have a long list of people ready to help, when all they have is your name on a sheet of paper.