Is devops a meme?

I like programming, and I like doing sysadmin work. Devops seems like a nice mixture of the two. And yet, the field seems pretty heavy on buzzwords and marketing speak - muh devops is a culture not a role - which turns me off. Is this a viable and desirable career path, or am I being memed?

Attached: Vos-Bencheurs-font-ils-du-devOps.png (1200x565, 46K)

Other urls found in this thread:

landing.google.com/sre/sre-book/toc/index.html
twitter.com/AnonBabble

What they mean by it’s a culture and not a role is that the whole organization has to be on board from the top down and not from the bottom up. If it’s just one dude in his office preaching the gospel of Infrastructure as Code, Repeatability and Containerization - no one will care or worse they’ll give it all to you. Trust me, you don’t want that.

This being said, were more like developers who understand infrastructure so at least at a non shit company you’ll still be developing something or other. I write lots of tools in Ruby, C, Java, Erlang and even Elixir

Why isn't it _actually_ explained anywhere what the fuck is DevOps? How can people that weren't born with the lingo in their heads figure out this shit?

When a person is "doing DevOps", what actually is happening? What _commands_ are they using?

Are they developing, then compiling some shit, then running the binary in a server? What the fuck is going on, what are the _actions_ performed?

Still coping with Agile, not ready for DevOps yet.
It's all '''''business''''' jargon meaning "werk moar user."

As far as I know it depends on the company just like "ux developer" or "full stack developer". From what I hear it is sysadmin but he can write scripts and actually program for special cases or is glue for software developer teams that can do the icky stuff the dev team/managers don't feel like doing.

SRE solidifies 'devops' from some of its lofty BS into more practical terms.

I have observed organizationally what it really means is that lots of sysadmin responsibilities get moved out of 'ops' organizationally and placed under development management. The work is similar honestly but the cohesion is better. Since the code is often tightly coupled to the os, even if just at the edges the code base.

.t SRE (ama)

Attached: 1452450499850.jpg (252x233, 18K)

How's you get a SRE job? Was it right out of school or were there some intervening jobs? If right out of school, what kinds of classes/internships did you take? If you had jobs in between, what (roughly) were they? Thanks.

Agile. Blargh. My master's program has a required Agile class. Really not looking forward to it.

i want a job like yours. What do i need to learn what are the best books or resources you recommend for it?

I have to respond to two job offers i've got.
The first is an IT/Cloud consulting company for AWS, GCP, Docker, Kubernetes ..etc to build resiliant elastic architectures with CI/CD support.

The second is a DevOps consulting company for the finance sector, things like Git, Maven, Jenkins ... Etc so it's only CI/CD most of the time.

Same salary, first one has more cool young people , which one would you chose ?

> Cool young people
Be wary of companies like that. Where do the olds go? Do they eat them? Push them off of bridges? Also, a good sign that the work life balance sucks.

However, AWS experience is gold. If you don't already have some, probably go for that, the above issue aside.

If you're a good sysadmin that can code his own tools, you're gonna have a great time in general.
All sorts of tedium in the IT world can be automated.

I know there will be a lot of work, but i just loved the guys, they aren't full of shit, no diplomacy, no bullshit policy, some dude from there literally presented some slides while drunk in front of Google personnel and kept saying that he forgot some stuff cause he's drunk ! How cool is that.

Compare that to the others who since the begenning started asking HR autism filter questions. Motherfuckers

I'm not autistic, i just don't like bullshit, i can pretend and play their game, but not 24/7 , that would make me go insane.

>Tfw too intelligent to work with normies.

They probably just use sql to maintain databases and then unplug then replug in an ethernet cable thats all they do

Oops

>How's you get a SRE job?
I was on a traditional development team that decided to spin off about 1/4 of its members to create an SRE team with some organizational buy in. I had previous experience as a sysadmin and spent time working with the sysadmins at our current role so when th team was created I was a natural fit.

>Was it right out of school or were there some intervening jobs?
Internal move, but I have interviewed for and got devops jobs right out of the gate before.

>If right out of school, what kinds of classes/internships did you take?
I never actually finished my degree, dropped out freshman year.

>If you had jobs in between, what (roughly) were they?
Took some time to work in traditional development. This was definitely a benefit to my resume and my code quality.

Specific technologies can be gleamed from job interviews. I would recommend Googles SRE book, landing.google.com/sre/sre-book/toc/index.html as well as Designing Delivery and Clean Code. TDD has become a lot more important as I work with the 'edges of the system' so to speak, interfaces and tests are increasingly important.

Both are consulting companies so its a bit of a toss up. I work in fintech and am very happy to work in that sector, stable and pays well. The first role sounds like it has cooler tech. Honestly I would probably pick the second one, because there are old people. While anyone can suck, sometimes you meet a real fucking wizard and can learn absolute career changing stuff from one project with someone. Even if you end up hating them.

The salary is the same (and it's a lot of money)
But i heard like banks and other finance companies use obsolete tech.

The first one is a Google partner, cloud native architectures are the future IMO.
It just makes sense.

Maybe i'll get some experience in the first, then go to the finance sector to introduce them to superior tech

Finance is not a one size fits all, if you're working for a bank it will be outdated. If you are working at a quant or prop trading firm you will have some cool low latency stuff and some of it inevitably will have to be newer. Usually lots of custom stuff in those kinds of places which bring their own interesting challenges, with a few resume gaps.
Where I work we generate over 12 billion rows each day, that brings some cool problems to work on solving.

You're in a win-win though, I'm sure either choice would benefit you. Good place to be, congrats.

Yeah it's mostly banks. What was a redflag for me, is the director of the DevOps teams of the fintech consulting firm didn't even know what's container orchestration ! WTF ?!

For info, I got lucky with my intenship where i used Kubernetes and GCP. And i know Git better than the guys who interviewed me in both companies.

Fresh out of reputable uni, this is my first job.

Let's see how it goes.

Fresh out of uni, definitely pick the wide consulting firm so you get exposure to as much as possible and a better idea of what you like.

#2 every day

this guy fucks

checkout terraform, nomad, packer, cloud formation for starters

I know what's going on in the market,
Programming sucks, it's slavery, don't see myself happy reading other people's code , there will be a lot of that.

I'm too qualified for sysadmin stuff, but it seems comfy, i'm basically looking for a comfy career, the least work/salary ratio possible.

DevOps opens the door to IT management careers too, i'm considering it despite me cringing everytime i hear Agile.

whatever impresses the client

>this guy fucks
I'm probably the most rebellious guy in my office with dickies and an untucked polo. Our webdevs started wearing tshirts and you can tell people look down on them for it.

DevOps just means you are doing 2 jobs while being paid for one.

>DevOps just means you are doing 2 jobs while being paid for one.
Smartest reply yet.

it's not a meme, there are key components that define whether or not you're using devops tools

they're using things like CircleCI, Slack integrations, automated testing, 12-factor methodology, Ansible/Chef/Puppet/Salt, etc.

It really depends on what you're building to define what devops tools you'll need

Eh, now you sound like a bit of a douche. I don't have the image but reminds me of a fairly common phenomena where you know everything very quickly, then find yourself humiliated with failure until slower mastery begins.

In my experience SRE/devops work is often more grueling, tracing, and learning then dev work or our devs would do it. I'm doing it because they need someone more attentive, knowledgeable, and most importantly patient.

Solving problems of scale isn't always some easy problem you throw someone else software at and kiss goodbye.

That's why it's the highest paying IT job

The old model of work was:

> Dev teams coded everything, then Ops teams packaged, deployed, and maintained it

This can lead to a bunch of issues as the Ops teams might not be able to support the usage since they don't know enough about the system's internals to know why it's acting up.

So, why not just have the Dev teams do everything except maintain the interstitial systems. This allows the Ops teams to just replace wholesale the component that is acting up and report the issue to the Dev team.

This allows you to hire more technically specific individuals for Dev while the Ops side can be farmed out or even replaced wholesale with a sufficiently advanced system (e.g. kubernetes and autoscaling means that you just need to hire someone that can deal with scaling and performance issues instead of a sysadmin).

>I'm too qualified for sysadmin stuff
lmao
You're never "too qualified", there will always be stuff that you don't know.

probably the most comfy place for a dev methinks. also actually committing something valuable that you own in production. less money based deadlines doing late nights because the sales team sold a years worth of work for 1month pay ..

Nope. The "DevOps" at my company make just as much as the devs. They are on the same job ladder.

>I'm too qualified for sysadmin stuff

top lel

Attached: 1508962489629.jpg (1561x2048, 319K)

it's a meme if you're a NEET

He said IT not dev.

Nah, you're too far gone in their bullshit user. Where the fuck you think you are normie ?

Nobody likes to work for others, let's not pretend otherwise.

I know my level, i wrote this year the virtual memory mapping functions of an x86 kernel, only very few people at my age did it.

I got a degree that literally makes me receive job offers on LinkedIn like a girl receives phone numbers on a troops train.

Why would i want a high stress job ? Shit i don't even want to work, i would prefer winnig the lottery

There are jobs you only get if you have a masters degree, sysadmin is not one of them

This is why we can't have nice things, bait.jpg

Traditionally a sysadmin was an upwards move from development. They Not only understood the application being developed but also the code of the operating system making them uniquely qualified to compile, deploy, and troubleshoot the application.

>They Not only understood the application being developed but also the code of the operating system making them uniquely qualified to compile, deploy, and troubleshoot the application.

That all changed when close-source software started getting deployed and the admins were shut out of development processes.

Devops is an odd return to form.

>Devops is an odd return to form.

More like the welcomed return. Since everyone is peddling open source software as a service its not so shocking they would need this again.

Sysadmin is a dead end, your servers will get replaced by the cloud, and your job will get outsourced.
I advise you to get AWS sertified if you want to last on the bizz

Personally, I'm always looking at what my next move is going to be (eg: the gig after the one I'm currently looking at). So I'm always looking to learn something new, so that I'm more valuable 6 months or a year from now. With that in mind, which one has smart people that you can learn from? Which one has opportunity for you to get good at something new (or better at something that you're already good at)?

Attached: mou.jpg (300x168, 10K)

Good point
The first one clearly, they are Kubernetes specialists, this is the best container orchestrator for the next 10 years. And it is very new. It'll look great on my resume.
With a couple of AWS certification.

The fintech has nothing trendy, IMO they are using obsolete tools and methods.

If you get past all the buzzword bullshit yes it's necessary and yes it's quite nice.

Really all it means is having an automated (or mostly automated) build and release system, ideally one that allows for continuous integration

and most importantly, easy reversion if you fuck up a release

>With that in mind, which one has smart people that you can learn from?

IaC. Terraform or PS-DSC if you're a Microsoft fag.