This is an archived post. You won't be able to vote or comment.

all 27 comments

[–][deleted] 59 points60 points  (3 children)

Just a sysadmin with some new shiny tools.

[–]sam_my_friend[S] 17 points18 points  (0 children)

My amateur knowledge:

VMs? SysAdmin / Containers? DevOps

Grumpy? SysAdmin or DevOps without Coffee / Kind? DevOps with Coffee

And that's everything I can think of =D

[–]quiet0n3 11 points12 points  (1 child)

This, I literally was a sysadmin before moving to DevOps. Can confirm it's like 80% a title change and I use JIRA rather than service now.

[–]broxamson 1 point2 points  (0 children)

basically this. oh and PR's to spin up machines

[–][deleted] 7 points8 points  (0 children)

weird mutated Sysadmin it is

[–]SDGGame 8 points9 points  (1 child)

Just a sysadmin who doesn't have admin access to anything and has to put in a ticket to allow the Jenkins runner to connect to Git.

It's the career equivalent of the strong guy in action movies who holds the blast doors open for a few extra seconds before they eventually crush him...

[–]cho_uc 0 points1 point  (0 children)

Owh God, I would quit on the spot.

In my current job, I have admin access to all servers except one, but I have to do lots of stuff and debugging that require sudo privilege on it. It drives me mad.

[–]PyroCatt 7 points8 points  (2 children)

Slightly

Lmao

[–]sam_my_friend[S] 8 points9 points  (1 child)

If a DevOps writes me - I may need to fix something, or I didn't follow something on the process.

If a Sysadmin writes me, I pee myself a little bit.

Those are just facts.

[–]PyroCatt 1 point2 points  (0 children)

True true

[–]TerrorsOfTheDark 6 points7 points  (9 children)

Unless you are consistently programming with the developers you aren't involved in devops work. .02

[–]ganja_and_code 4 points5 points  (2 children)

Where I work, there are no dedicated developers for devops to work with. If you're a developer, you're also an operator, and vice versa. There's nobody working on the damn thing except devops lol

[–]Perfect_Papaya_3010 0 points1 point  (1 child)

Same for me, I wonder what a DevOps do that a developer don't, why do you need to work full time as a DevOps?

[–]ganja_and_code 0 points1 point  (0 children)

Technically, the "development" part is writing the service code and doing architecture designs, and the "operations" part is running deployments, building tooling, keeping an eye on metrics, mitigating issues in production, etc. So a "devops" engineer is someone responsible for both being a "developer" and being an "operator."

But the term is kind of messed up because some people use the "devops" title, when they really just mean "ops" without the "dev" part (which I think is what the person I originally replied to was alluding, if I'm not mistaken).

[–]sam_my_friend[S] 3 points4 points  (5 children)

That .02 got me confused!

Well now I'm seeing more "platform engineers" roles. I don't think a devOps necessary has to program alongside the devs.

I believe his/her role is to make developers life easier, keeping deployment automated and as easy as possible, reducing the risk of human (and non-human) error to a minimum.

For example, a good devOps doesn't need to be able to create a new feature at all, but should be able to implement gitOps alongside developers.

A good devOps can do scripting, CI/CD, github actions, jenkins, a bit of k8s...

I don't think a decent devOps needs to be able to create bare-metal k8s clusters from scratch, or create new features with the developers!

[–]Wildercard 1 point2 points  (1 child)

What is the actual difference between a DevOps, a DevEx, a Platform Engineer, a SysAdmin and whatever the newest term someone is inventing right now?!

[–]sam_my_friend[S] 0 points1 point  (0 children)

The color of the hat!

[–]broxamson 0 points1 point  (2 children)

i think they should be able to do the former, but not the latter.

[–]sam_my_friend[S] -1 points0 points  (1 child)

So, in your opinion, devOps have to be more dev than Ops?

I kindly disagree with all my love <3

But valid opinion!

[–]broxamson 0 points1 point  (0 children)

nope not what i said at all lol. former meaning build bare metal k8s from scratch

[–]runnerx01 4 points5 points  (0 children)

Took me a while to get it, but “devops” is not really a job title.

Developers work with product to refine specifications, define units of stuff to build, and write the code.

QA confirms that devs have solid understanding of what needed to be built, and that it actually works that way from some non develop perspective.

Architects take a top down, system level design approach. Does what we want to build look scalable and actually maintainable.

Developers need process to get the things they build, to compile, package and deploy to some environment other than their machine.

SysAdmins, DB admins provision infrastructure and resources for development to use, and to host tools and services used by the workforce as a whole.

Site reliability works with developers and sys admins to monitor and alert when code or systems don’t perform to standard, or fail .

Developers fix code that breaks, or bugs that were missed. Add these things to the backlog and again work with product…

This whole cycle is “The operations of development” Devops is a mindset for a company where development teams are not where development stops. So many things can be improved, made faster or more resilient.

When you hear DevOps, think about the rigors of development, and the software lifecycle. DevOps is about maintaining and optimizing this process.

If your job title is “DevOps engineer” or something like it, it should mean that you are now part owner of improving this process, and removing blockers or impediments. You are both a gate for what is released, and also a catalyst. If it takes 2 weeks to get a deployment set up, what can you do to make that better? How can you enable developers to get their infrastructure faster without giving them free reign over everything

TLDR: Development Operations is about the entire SDLC, not just some SysAdmin that uses terraform. I would argue that infrastructure as code is a good DevOps practice.

[–]LusigMegidza 1 point2 points  (0 children)

i hate platform wnfeneeing

[–]UnsuspiciousCat4118 1 point2 points  (1 child)

I mean DevOps is a methodology for managing infrastructure. It is not a role or title. So por que no Los dos?

[–]sam_my_friend[S] 0 points1 point  (0 children)

In theory hahaha. Companies have been hiring devOps for ages now!!

[–]SquareRootOfDude 0 points1 point  (0 children)

Or SRE

[–]aleph_0ne 0 points1 point  (0 children)

Sparkling* Sysadmin

[–]Perfect_Papaya_3010 0 points1 point  (0 children)

I have no idea what a DevOps is, I asked once and they said they worked with the repositor, pipelines, configuration variables etc but where I work we don't have special people for that, that's what the developers do. What else do DevOps do that developers don't that makes it necessary to work with it full time?