← sources

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?

source: reddit (reddit:devops)published 2026-11-15 17:46ingested 2026-11-16 02:35

retained text

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?

document fetched 2026-11-16 00:24 · canonical https://reddit.com/r/devops/comments/1xx1rr7/when_a_vibe_coded_internal_tool_ends_up_with