Ask HN: How do you handle non-technical people dumping vibecoded changes on you?
A recent trend at work involves non-technical individuals creating features using Claude Code and seeking reviews from technical staff. While this approach allows for clearer communication of ideas, it raises concerns about the quality of the code and the responsibilities of software engineers. The situation presents a dilemma between embracing innovative prototyping and maintaining professional standards.
- ▪Non-technical people are using Claude Code to create features.
- ▪They often seek technical staff to review and submit their work.
- ▪This trend raises concerns about the quality of code and the role of software engineers.
Opening excerpt (first ~120 words) tap to expand
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.
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.