How do you handle non-technical people dumping vibecoded changes on you?

Question

I've started to notice a trend at work recently where non-technical people will vibe-code a feature on their own with Claude Code, then come to you and say "hey can you review this and help me get it committed"Would you go along with that or push back?On the one hand its useful in that they can much more clearly express what they want from the feature since they have prototyped it in the real product. More clear than a document.But on the other hand it feels like a slippery slope. It would suck to have your job as SE devolve into fixing other people's vibe-coded spaghetti.

kspetkov79 · Accepted Answer

I would not treat it as code to merge. It is closer to a rough spec that happens to compile.

jsh76 · Answer

Give them time, resource requirement and budget to get it done right. eg: I need 16 ppl, 2 mil and snacks for my cat. What non tech people bring to the table is extra resources. If they whip up whats required then who cares if prototype was vibe coded or drawn with crayons.

innagadadavida · Answer

I think you need to give them visiblity on how long it will take to review, test and understand how it works and the risks so engineering feels comfortable being on the hook for it.