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

Non-technical employees are using AI coding tools like Claude Code to build features independently, then asking software engineers to review and submit the code. Engineers report that while these prototypes help clarify feature requests, the practice creates a slippery slope where developers may end up fixing poorly written AI-generated code rather than building their own work.

| |||||||||||| 4 points by | 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 submitted" 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 crap. | ||||||||||| |