this post was submitted on 11 Mar 2026
138 points (97.3% liked)
Programming
26022 readers
326 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Do NOT under any circumstances fix it. The other guy needs to and you need to be clear he broke it and how
I came here to say exactly this. The offending dev and your manager aren't going to understand the severity of issue until he spends days trying to find the bugs. Not your circus, not your monkeys.
I would immediately fire somebody with such a mentality. Letting bugs live in production just to prove your point, that's borderline criminal. I get you're not happy with the vibecoder's job but there are other, smarter ways to deal with this than sabotaging the company.
Gunna be honest, if you really feel that way you'd fire the vibe coder. I don't give a shit if it's broken ifs due to the negligence of management and other employees.
Poor planning on your part does not constitute an emergency on mine. And ofc this varies based on the service as all things do. But it's rarely important enough that I'd stay over. Like if lives where at risk or it's a "bring the company down but" maybe I'd stay. But there would be hell to pay for whoever broke it later. Either that or the company would loose me as an employee
These bugs shouldn't have reached production. This is why you do reviews in chunks.
Probably very true (again, it depends on the product/company).
By that logic wouldn't you be firing the vibe coder for not rolling back the commit?
Fallback and fix is the best solution.
Maybe. Context is not sufficient (mistakes can happen, intention counts) but breaking prod may be bad depending on the product type.
Other ways such as?
I dunno, human things like communication and letting people know what's wrong here and how not to let that repeat. If it's pathological then maybe that work environment is not fit for you.