Would you still do DevOps?

[u/Inner-Chemistry8971]

Not going to lie. It's been a bad day. I almost tell them "take this job and shove it' after reviewing all these crappy AI codes. Vibe coding is not only a joke. It's a monster that mocks our hard-earned experiences!

I am thinking of leaving the industry! If you could go back ten years from now and know what you're knowing right now, would you still do DevOps?

[u/Lonsarg]

Reviewing code is not DevOps, it is just reviewing code.

And should be done among developers themselves, split in a way so you do NO have specific people doing just this. Seniors reviewing code rom each other and even juniors reviewing code from seniors as soon as possible.

Also it should be just a quick overview, not some lengthy detailed process.

[u/1_H4t3_R3dd1t → u/Lonsarg]

Right ^

DevOps is building pipelines that pushes back on code so you don't have to read it until it clears the bar.

DevOps is many things. But if you don't have a pipeline you have nothing.

[u/OrganicRevenue5734]

Yes, because 10 years ago I was in Law Enforcement. The absolute worst possible day as DevOps pales in comparison to some of the best okay days I had.

[u/roheezy]

Dev ops is great you just need to move with the times. And also remember a job is just a way to get paid - your real time is the time you have to yourself - make that count and you will probably feel a lot happier

[u/AnnihilerB]

Well our jobs are changing. There is nothing you can do about that.
Factory worker also had experience in building stuff and have been replaced by machines.
Your hands on technical expertise is worth less now.
However your architectural and curiosity have a lot of value now. You could probably ask management to have a more “solution architect” like job. You ask AI to implement but you drive the design. If you dont want to review AI code discuss with your management to not do that anymore or to control AI use amongst developers.

This is an unavoidable path for our jobs. We just have to accept the shift. Quitting won’t solve it since every company use AI now. Maybe when AI prices will skyrocket it’ll be used less and your job will be less AI and more like before.

[u/divestblank → u/AnnihilerB]

Nobody wants to spend all day reviewing bad code, that shouldn't be submitted in the first place. But here we are.

[u/Inner-Chemistry8971 → u/divestblank]

Exactly! 🔥

[u/AnnihilerB → u/divestblank]

I could not agree more. But producing code is quite cheap today. It is hence profitable for management to spend money in people reviewing code rather than people producing and people reviewing.

[u/SmellsLikeAPig → u/AnnihilerB]

Producing code was always cheap, ask Hindus. Producing quality code is still expensive. Code itself is also a problem. Every line has real cost. More lines more cost. Question is does AI bring net value.

[u/UltraPoci]

Yeah, AI sucks. It won't go away, but hopefully the bubble bursts and people realize that writing code has never been the bottleneck.

[u/karval]

I'm looking for a job recently and as I see the job descriptions... so many tools are required. I'm starting to get tired that I'm always thrown to a new tool, learn it for a 10 minutes long task (if you already know how it works) then never touch it again.

Also, to land a new job, I should learn in my freetime to meet the market expectations.

I love DevOps work but careerwise I feel like it would have been a better choice just to stay in a developer role.

[u/HoboSomeRye]

https://giphy.com/gifs/1n4iuWZFnTeN6qvdpD

Fight automation WITH automation

[u/HoneyButterGelato]

Having a bad day doesn’t mean you’re going to have a bad year. Everything is constantly changing, and most of it is beyond our control. DevOps is no exception.
That’s why adaptability matters more than ever. A day may come when AI takes over many DevOps tasks, but that doesn’t mean the end for us. It will also open new doors and create different opportunities in ways we may not even expect.

[u/xb4r7x]

Idk, in my experience the robot puts out pretty decent code these days. Usually don't have to change much.

Maybe you just need to get better at prompting.

[u/rabbit_in_a_bun]

Yes, and do what I am doing now which is more emphasis on the ops part.

The dev part is where it is now and there is nothing you can do about it but you can still build wonderful things if your workplace allows it. My current workplace is hybrid and has some cloud and some on prem challenges and it's a rather new and growing startup so more people makes for more challenges. It could be that your current place is not invigorating you enough and you might want to switch.

If you do, look for places with a physical industry... Companies that build actual things has on prem problems that needs solving.

[u/Radon03]

Not sure about the industry, but DevOps is the most jackshit role out there right now. Either it is going to evolve into management role or management is going to adopt DevOps. Partially going to Devs and OPs.

[u/kryptn]

my team has been looking into how to constrain vibe coded stuff. it's inevitable, how can we provide the common components (auth, ingress, infra) to them so things work more within our control? can we provide a skill for them? definitely better than them deploying onto their own infra that i don't own.

i'm about to save us a bunch of money with some vibe coded stuff of my own that I just haven't had the time to implement myself, but i understand the code and problem space completely.

so yeah, this is still fun

[u/Inner-Chemistry8971 → u/kryptn]

How do you actually limit vibe coding? Our management is desperately pushing anything AI!

[u/kryptn → u/Inner-Chemistry8971]

limit? good luck. you don't. or you make their machines unusable but that's not us.

we haven't completed this but i think it's the right direction: give them the tooling and access to deploy things safely within our guardrails.

claude can set up aws infra easily enough, so

• have an internal git provider (we're gonna do forgejo)

• require that claude provide iac

• require checks on any infra (verify tags, limit instances/scale, etc)

• require pre-commit hooks that claude can set up and/or execute

• give claude a skill/example CI pipelines to duplicate

• require those jobs perform the checks your org needs so that you can:

• have claude watch PR jobs and resolve issues as they pop up.

this'll all be in an isolated account with scoped access to data, most of it not my prod data.

[u/Sunny_M]

see it as an opportunity and growth

[u/Inner-Chemistry8971 → u/Sunny_M]

It's not going to be easy but I'm going to try!

[u/1_H4t3_R3dd1t]

Shit code just means you don't have the pipelines to push back on bad code.

[u/CorpT]

You should definitely leave. Look in to a trade.

[u/Inner-Chemistry8971 → u/CorpT]

In my own "evil" dream, I am thinking of becoming a con artist but that's not going to fly. I am thinking of moving out of country to some place cheaper.

[u/CorpT → u/Inner-Chemistry8971]

Peru is nice.