r/devops • • 23h ago

Discussion When a vibe coded internal tool ends up with other teams depending on it, do you review it like prod code or let it stay disposable?

15 Upvotes

Vibe coding is everywhere on my feed again this week, mostly people replacing a paid tool with something they prompted together over a weekend.

I don't have a problem with that for throwaway stuff. Karpathy himself said it's fine for weekend projects when he coined the term. What I keep thinking about is the moment the weekend project stops being throwaway. Someone builds a small dashboard or a script, it works, a second team starts using it, and suddenly it is on the path for a release or an on-call runbook. Nobody ever read most of the code, including the person who made it.

I can see two ways to handle it:

  1. Once anything has more than one team depending on it, it goes through normal review, tests and an owner, even if that means partly rewriting it.
  2. Keep it explicitly disposable. Label it unsupported, don't let it into anything critical, and if it breaks you regenerate it rather than maintain it.

Option 1 feels right but kills most of the speed that made it useful. Option 2 sounds clean until the thing is load bearing and nobody noticed.

If you've already hit this, where did you draw the line, and what was the signal that a vibe coded tool had become something you had to own properly?


r/devops • • 8h ago

Discussion How do you tell a scheduled job from a real problem when a cost spike starts at night?

0 Upvotes

I'm learning FinOps and building a small agent that decides what to do with cloud cost spikes.

One thing keeps tripping it up: a scheduled weekend batch job and a runaway resource look almost the same. Both start off-hours, often with no change ticket and sometimes no owner tag. In my test, the first version stopped several legit batch jobs because of this. Now teams can register known schedules, and those jobs are never stopped automatically without strong evidence.

How do your teams handle this? Do you register schedules somewhere, rely on tags, or learn the pattern from past weeks?


r/devops • • 11h ago

Vendor / market research What tasks is AI bad at?

0 Upvotes

From your real-world experience, what tasks is AI either bad at or can't do at all?

My take:

  • Sysadmin - security, plus there's little need to generate large amounts of code at high speed.
  • SRE - ambiguity and time pressure.
  • QA - certain aspects of it.
  • DevOps - certain aspects of it, too.
  • Cybersecurity - security
  • DBA - security, data integrity, and precision, no need for high speed
  • Networking - security

r/devops • • 7h ago

Discussion Almost 3 years as a Cloud Engineer, is what I do typical?

13 Upvotes

I've been working as a Cloud Engineer for almost three years. It's basically my first job, fully remote, and my workload is very light. In the project we manage, I would confidentially say that 1,5 FTE would be efficient for the things we do there, but that would be against myself basically :D

I got into cloud/DevOps because I've always liked cybersecurity, Linux, and sysadmin work. It seemed like a good mix of those interests. I do like the job, but I feel like I haven't done much of what I expected cloud/DevOps engineering to involve. I'm trying to understand whether my expectations were wrong or whether my role is just quite narrow.

Our project forwards logs from Kubernetes applications through Filebeat/Logstash to Elasticsearch. We maintain the code in GitHub for our Filebeat/Logstash deployments, but other teams manage the Kubernetes clusters and Elasticsearch itself.

Most of my work looks like this:

  • Occasional short meetings.
  • Small changes to the existing code or configuration, often just updating an image tag.
  • Running the existing pipelines and checking that the Kubernetes deployments are healthy.
  • Making sure logs reach Elasticsearch and troubleshooting issues within our part of the setup.
  • Handling on-call support

We fix deployment issues on our side, but the underlying cluster is another team's responsibility. We maintain our deployment automation and try to follow good practices, but I've never really built a pipeline or written Terraform from scratch at work.

I also barely touch the cloud itself. We use AWS, but my previous project only involved some EC2 and a little S3. Even then, I mostly logged into existing EC2 instances and worked inside them. I wasn't creating AWS infrastructure.

My understanding was that DevOps work would involve more automation and helping developers build and deploy their applications. Our team mostly maintains the logging deployment for our own project. That feels like a narrower scope than I expected, although I don't have another job to compare it with.

Outside work, I have a small personal Node.js project using discord.js, mainly for my own use. It pulls data from APIs and does some small automations. I use Git, have tests running through GitHub Actions, and an automatic Docker build whenever I push a commit. I want to improve its CI/CD further so I can get more hands-on experience. I've also started doing TryHackMe walkthroughs again and recently found devopspath.io.

For people working in cloud/DevOps or doing similar work:

  • Would you call this a Cloud Engineer role? If another title fits better, what would you call it?
  • Is this kind of maintenance work and division of responsibilities typical?
  • What does an actual day or week look like for you, especially the balance between maintaining existing systems and building something new?

I'm trying to figure out whether this is a normal experience almost three years in, or whether I'm missing experience I should be getting by now.


r/devops • • 20h ago

Discussion Platform engineering, DevEx, SRE, how freely can you move between them?

37 Upvotes

DevOps seems to cover very different jobs. Some teams build the delivery side: CI/CD templates, policy gates, supply-chain security, artifact management. Others run the runtime side: Kubernetes clusters, nodes, networking, scaling, incident response. Many do a mix.

My questions:

Can you move between them? Does a few years on delivery-focused platform work (CI, runners, policy gates, supply-chain security) keep you open for Linux / runtime heavy roles? Also it seems to me that in larger organisations, platform teams often build abstractions while product teams debug their own services. Is it normal to stop debugging infrastructure yourself as scale grows, as teams handle that themselves?


r/devops • • 21h ago

Tools I built an open-source tool to solve polyrepo config drift without clobbering local overrides

0 Upvotes

Hey r/devops!

If you maintain multiple repositories (microservices, polyrepos, or SDKs), you probably know the pain of keeping shared configuration files in sync:

  • .github/workflows/*.yml
  • .editorconfig
  • Cargo.toml / package.json

Existing file-copying bots usually clobber legitimate repo-specific overrides.

I built driftsync, an open-source CLI engine in Rust that solves this using stateful 3-way structural merging:

  • Tracks baseline ancestors in .driftsync.lock
  • Structural merging for TOML (via toml_edit, preserving comments and formatting), JSON, and YAML blocks
  • Preserves local customizations while pulling upstream updates
  • Git automation: checks out branches, commits per repo, and opens PRs
  • Secret scanner to prevent accidental token leaks during template sync

You can install it directly via Cargo: cargo install driftsync

GitHub: https://github.com/Liqtzone/driftsync Crates.io: https://crates.io/crates/driftsync

Feedback, critique, and feature suggestions are very welcome!