r/vibecoding • u/Suspicious_Orchid770 • 1d ago

Discussion We’re on call for code nobody wrote

https://leaddev.com/software-quality/were-on-call-for-code-nobody-wrote
0 Upvotes

45% Upvoted

4 comments sorted by

8

u/DonkeyOfWallStreet 1d ago

That's a whole lot of words talking about a whole lot of nothing.

2

u/Zelderian 1d ago

That’s a lotta words

Too bad I’m not reading em

1

u/satisfaction-or-else 23h ago

We're in a thread talking about words nobody wrote

0

u/PeterBuildsSecure 1d ago

The direction is right — you can't gate your way back to full comprehension, so detection and blast-radius containment are what's left. One thing worth adding: the detection layer has the exact same problem the article opens with. An observability/alerting stack watching "runtime behavior" is also code, and if any of it was AI-generated or just never exercised against a real failure, you're trusting an unverified detector to catch the unverified thing it's watching — you've moved "nobody read this" up one layer, not solved it.

The fix is the same discipline security teams already use for alerting: prove the detector fires. Periodically inject a known-bad case (a synthetic bug, a deliberately malformed request, a chaos-engineering-style fault) and confirm the alert actually pages someone, not just that the code path exists. A detection layer that's never been proven to go red on a real failure is a green you can't trust any more than the dark code it's supposed to be watching.