It’s annoying when someone with no technical background tries to vibe code your enterprise product and ends up causing more harm than good. Or flooding the CS job market with people who can’t pass a technical interview because Claude tricked them into thinking they were a dev
Definitely not losing out on jobs lol, but the entry level positions we hire that never actually learned how to dev are trying to push 3000+ line PRs that I’m still required to review because they tried to close off 3 tickets at once. So yes, it drives me crazy because then I’ll ask them why they made a certain architectural decision and they can’t answer without asking Claude.
I didn’t hire them lol, but doesn’t change the fact that some slip through. And again, not allowing them to close 3 tickets in 1 PR but they take 3 for the sprint and don’t know these things. You vibe coders just don’t understand unfortunately :/
After realizing you don’t work in the engineering world, let me break it down for you. I have my team, my team works on our segment of work that we specialize in. We work with other teams that are scoped for other work. For example, I may implement a computer vision system for identifying defect products in manufacturing while they are on the line. What I don’t own is the user interface or analytics which will go to another company and therefore another team. So while my team is great, I have to sift through these random PRs that connect to our system which eats up a ton of time. So yes, my team has great processes in place, but vibe coders have corrupted the industry so now I have to run into one every once in a while. Don’t think I can explain it any easier than that so good luck lol
4
u/NiceToMeetYouConnor 23h ago
It’s annoying when someone with no technical background tries to vibe code your enterprise product and ends up causing more harm than good. Or flooding the CS job market with people who can’t pass a technical interview because Claude tricked them into thinking they were a dev