Normal view

Today — 9 March 2026Main stream

How are you handling an influx of code from non-engineering teams?

Obligatory not trying to sell you something. 😂

I’ve been around long enough to make it through a wave or two of low code/no code tools including things like UiPath back when it was a desktop app and had no AI smarts.

Now, not only do engineers have access to Claude Code et al, but accounting, finance, and Human Resources all have access to the same toolbox. And some are vibing away!

Our engineers understand there is more than just building a shiny UI in a container and that there are considerations for where it’s hosted, how it’s secured, where the code is hosted, and who is going to own the thing not to mention who’s going to vibe in a browning code base. The vibe coding population has told their LLM of choice that they’re not engineers and it’s happily barreling them forward to get things deployed all of that be damned.

How are you handling all that? I’m finding the idea of documentation (how to build and how to deploy) welcome, but also encountering folks who are way out over their skis but pressing on with personal GitHub accounts, free plans on various AI first hosting platforms, and deploying to cloud hosting providers they found the keys for and were previously unknown to ops. 😬

I’ve worked in orgs with strict governance but my understanding even of those orgs is that the AI bug has infected many. Trying to balance ‘hey, let’s slow down just a bit and get this managed properly’ with ‘oh, very important people saw you demo that flashy solution and want to know why it’s not immediately available’.

What’s working or not working for you in this area?

submitted by /u/rayray5884 to r/devops
[link] [comments]
❌
❌