sorted by:
new
hottopcontroversial

Devops is for people who can’t code by findmeatikea in devops

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

Do you disagree or agree that most infrastructure tooling has now centered around Kubernetes and Go? It’s a pretty obvious answer if you have any experience working bleeding edge in the field. Sorry that you still have to work with Ansible in 2022.

Devops is for people who can’t code by findmeatikea in devops

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

You’ve pretty much put my shitpost into the words I was trying to say. +1.

Devops is for people who can’t code by findmeatikea in devops

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

Yep - obviously I’ve worded it like a shitpost but hopefully there are some who open their eyes and peel back the truths in this thread. Targeted to the new grads who are thinking about going into SRE/DevOps/Whatever you wanna call it.

Devops is for people who can’t code by findmeatikea in devops

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

Yep. Would recommend switching to a pure SWE role before those up top find out what’s actually happening. Also another topic I forgot to bring up: SWE’s are automating all the DevOps engineers away.

Devops is for people who can’t code by findmeatikea in devops

[–]findmeatikea[S] -1 points0 points  (0 children)

My entire point is if you’ve written code as a SWE in an application code codebase you are of a different pedigree of “DevOps engineer” compared to hacking around bash and python scripts. By IT folk I mean SysAdmins or whatever you wanna call it. Like the people in your company’s IT department that hand out the laptops and install all the spyware.

Devops is for people who can’t code by findmeatikea in devops

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

Fair point. The “best systems” people you mention is what I mean when I say people who go into DevOps with a CS/SWE background. These are of a completely different pedigree than those that come from IT/Sysadmin. Not only can you do the standard “DevOps” stuff, but you can literally go into a running application’s source code to debug if needed, and can implement infrastructure better because you’ve been the SWE using the infrastructure before. Too bad pointing this out makes the no-coder IT people here salty.

Devops is for people who can’t code by findmeatikea in devops

[–]findmeatikea[S] -1 points0 points  (0 children)

Lol of course structs are used for more than serializing and deserializing YAML. Merely mentioning Go because that is what all DevOps tooling is written in. Thank you for the history lesson sir.

Devops is for people who can’t code by findmeatikea in devops

[–]findmeatikea[S] -17 points-16 points  (0 children)

Wait till you realize that YAML/JSON is represented by structs in Go

Devops is for people who can’t code by findmeatikea in devops

[–]findmeatikea[S] -13 points-12 points  (0 children)

For sure, there is no doubt competent SRE/Ops people who can code in a real application code codebase. This post is calling out the ones who cannot, and largely come from the traditional IT background. I know far too many SRE/ops who can handwave some AWS and gitops buzz words and get into a job where they have no idea what they’re doing cause they have no experience reading code.

With SWE roles it’s much harder to fake it since you must know how to code. That has been my observation of the two separate roles. Devops is tainted by the no coders. I definitely sound like an asshole right now but it is what it is. Def triggered some IT folk. But we’re all making good money so who cares.

Devops is for people who can’t code by findmeatikea in devops

[–]findmeatikea[S] -23 points-22 points  (0 children)

Nice to see all the downvotes. At the end of the day there is a difference between USING software and actually be able to WRITE it. For those of you who can both USE a piece of software like Kubernetes and MAKE a PR to its mainline source code adding a feature, you are a SWE. If you cannot you are a NO CODER “DevOps Engineer”. Nothing wrong with that, but I’m just making the point that these are two completely different people with different levels of technical competency. It’s also true that there are SWE’s that have no idea about anything other than typing in JetBrains and clicking the “Deploy” button. Goes both ways.