devops should be paid 5x more then devs, they are literally expected to do everything, know every single programing and scripting languge, understand networking, iaas, automation, db and list goes on
devops should be paid 5x more then devs, they are literally expected to do everything, know every single programing and scripting languge, understand ...
Falling into your wing while paragliding is called 'gift wrapping' and turns you into a dirt torpedo pic.twitter.com/oQFKsVISkI— Mental Videos (@MentalVids) March 15, 2023
>devops should be paid 5x more then devs
clicking though few menus on AWS is unironically easier than being a clean coder though
You don't even have a fucking job, stfu if you're going to be a neet tripcoder.
I've never worked with a DevOps nagger that was anything beyond a midwit. DevOps homosexuals are just people that have read enough documentation to be useful, once you've implemented IAM for one org, it's literally exactly the same in every other org.
>Doesn't have a trip
Newhomosexuals get out.
writing service code is unironically easier than managing cloud permissions
> Using the console to spin infra
you don't spin up or manage infra by clicking button you absolute newb retard. you don't know what it takes to serious infra. you clearly don't have a job
Good ones are paid as much as devs.
>networking, docker, linux, bash, aws, a couple of languages
This is basic bitch shit that every developer should know.
>every developer should know networking, linux, bash
Networking and linux are huge subjects and developers are not supposed to know these like devops.
If you're a developer who doesn't know Linux or networking then you are hard-capped at junior engineer
Read what I wrote again (sorry if my english isn't good).
A developer doesn't know Linux and Networking like Devops, not even close, the knowledge gaps are huge.
Anon that's like saying that devops people don't need to know how to code
Not what I implied
it's not the same at all and you know it. god this place is tiresome.
There is no justification for not knowing networking as a developer. Even if you are the most autistic iToddler Xcode-nannied fagdev, you still have to understand the basics of networking. even if you're Python Andy scraping a website, you need to know networking. if you are pushing to git, you should know networking.
Linux is less essential but the idea that modern devs should ignore it is like telling people to avoid their driver's license because they can drive a golf kart to work instead.
>you still have to understand the basics of networking
That's what I said earlier, devops knowledge is NOT basic - at least in networking and linux.
i think it's perfectly reasonable to expect devs to understand the fundamentals.
is it reasonable for them to understand how their locally running service connects through the ZTF to our backend gateway to the staging cluster to a specific node which in turn networks to a container? probably not.
you don't have a job though, hobbyist freetard
You Azure, GCP, ARM templates, BICEP, CDK, Cloud Formation, Ansible, YAML, TOML, Terraform, Kubernetes(AKS, EKS), Openshift, RHEL, Powershell, Bash, Active Directory(Kerberos, SAML, OAUTH, LDAP, Azure AD) I could go on...
>Azure, GCP, AWS, Fucking Alibaba
Most DevOps naggers specialize in a single service provider. At which point it's just a case of reading the docs.
>ARM templates, Cloud Formation, Terraform
Everyone just uses Terraform. Even if they didn't it's not like repeating the same ~1000 loc is hard
>Ansible, YAML, TOML
No hard to learn, maybe a weekends work.
Admittedly setting up EKS is a pain in the ass.
Again, trivial. It just syntax, there's nothing hard in learning that.
>Active Directory(Kerberos, SAML, OAUTH, LDAP, Azure AD)
It's not like you need to intimately familiar with the implementations and specifications of any of those. DevOps naggers just need to know what buttons to press to get it working. Again, trivial, read the docs.
>t. former DevOps nagger
I used to do fullstack and for a while did only DevOps, I hated it, the most mind numbing, tedious bullshit I've ever done. Moved back to development after that. Nothing will ever pry me away from my precious backend ever again.
>Bro just read the docs lmao
How is this any different to devshit? Just read Spring/Node/Django/React/Postgres docs and rearchitect the entire company application bro lmao.
I hate this website.
>How is this any different to devshit?
Because in development the docs only tell you "this function expects these arguments". They don't detail the logic that you might be expected to implement. Now lets look at DevOps, anon mentioned setting up EKS, which is probably the hardest thing on that list. Oh look:
And there you go, job done. in dev land, reading the docs is probably the beginning (or more likely in the middle when you're trying to debug something)
>in dev land, reading the docs is probably the beginning
I think your job as "devops" wasn't serious at all
Keep coping, DevOps is a meme job for midwits.
If you had any experience with this, you would know that documentation is generally wrong and outdated, nothing works like it should, and you have to debug it yourself.
True but in reality most webshitters don't know any of it. Even backend devs may not know much outside their heavily-abstracted framework of choice.
yes. but docker/kubernetes is absolute shit.
It's easier for developers to setup devops processes than it is for devops to develop code.
Everything you use as a devops guy was thought through and developed by developers. You are using finished products, fine tuning them for advanced usages, making your own scripts, troubleshooting and eventually making a pipeline that can execute a certain workdlow.
You are nothing more than a user.
Devops is IT for developers.
This post is either bait or you are millions of light years away of realizing how much you DON'T know.
Go read about Dunning-Kruger effect.
>system engineer/devops for the last 3 years
You literally just described programming.
>It's easier for developers to setup devops processes than it is for devops to develop code.
No, not really.
Developers will find it easy to setup trivial devops processes in these same way that DevOps will find it easy to write simple scripts and urgently patch retarded security bugs in production because the original contractor left and the company doesn't want to pay for another one.
all these categorizations about software development and bitching about knowledge are what made me realize the bell curve is real
Is devops stressful? Do you work more or less hours than your peers in different professions?
If you want a easy life just become a security guard, won't get anywhere in technology if you aren't willing to put the hours in.