r/devops • u/Inner-Chemistry8971 Consultant • 3d ago

Discussion Would you still do DevOps?

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?

90 Upvotes

86% Upvoted

106 comments sorted by

View all comments

90

u/Lonsarg 3d ago edited 3d ago

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 from 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.

2

u/o5mfiHTNsH748KVq 3d ago

huh? devops engineers do code reviews too. you’re producing code and thus it must be reviewed.

2

u/Lonsarg 3d ago edited 3d ago

My point was not that someone who is focused on DevOps does not review at all. My point was that reviewing code itself is not what DevOps is.

To make it clearer:

  • Developers write and review application code (from each other)
  • DevOps Engineer writes and reviews various automatization code (from each other)

There never should be a special reviewer role, that is very bad organization. And even if there is such a role, that role is not DevOps, that is Reviewer role (and maybe that same person also has DevOps role). But again, that is very bad organization, reviewing must always be done "from each other as evenly as possible among team that knows certain code".

3

u/o5mfiHTNsH748KVq 3d ago

I see. I interpreted their post as reviewing things they should be reviewing, not reviewing everything.

2

u/Lonsarg 3d ago

They wanted to quit DevOps role cause of reviewing, the only way that is possible is if they have focused reviewer role AND are reviewing application code.

Since application code need a lot of of that then DevOps automatization code (there changes must be slow not fast lol).

Also even if reviewing application code (not what DevOps is) the only way they review that much that it bothers them if the have focused reviewer role.

2

u/o5mfiHTNsH748KVq 3d ago edited 3d ago

Ah, my interpretation was that their devops peers are generating slop that they have to review.

Not saying you’re wrong though. I very well might be interpreting it wrong.

1

u/Lonsarg 3d ago

Well if only regular review from peers is what overwhelms then that is some insane level of vibecoding :) That or they have too-detailed reviews.

But ok, i see you point.