I am someone with kubernetes in my job title. If you as a developer are expected to know about kubernetes beyond containerizing your application then your company has set itself up for failure. As you aptly said kubernetes is an ecosystem, and the dev portion is a small niche of that.
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
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:
they don’t know what they are talking about
the company behind the offer puts a lot of meaning into titles, which means things will likely be pretty hierarchical even though they claim it won’t be
they’ll likely try to pay you less that your worth
Hence, they invented the DevOps “Role” because it sounds more modern.
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.
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.
but I never got the job, so I guess idk.
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.
I swear Im a decent coder, but fuck me if kubernetes and that whole ecosystem just confuses me
I am someone with kubernetes in my job title. If you as a developer are expected to know about kubernetes beyond containerizing your application then your company has set itself up for failure. As you aptly said kubernetes is an ecosystem, and the dev portion is a small niche of that.
Wait, shouldn’t the developer know how to scale their application, debug networking issues, etc?
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.
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
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.
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.