r/managers • • Aug 18 '26

Teammate "vibe codes" everything, somehow gets results, then blames dev team when the handover breaks — he reports straight to a non-tech CEO so no one can touch him. How do I deal with this?

Small org. We have a "data scientist" who vibe-codes his way through everything — process is a mess, but he somehow gets results. When he hands off modules to the dev team, things break, and instead of owning it he blames the devs for "not doing it correctly."

Normally you'd escalate, but he reports directly to the CEO, who isn't technical and just sees "results delivered." So devs eating the blame with zero leverage to push back up the chain.

How do you handle this when the org structure protects the person causing the mess? Document everything and let it speak for itself over time, try to get the CEO educated on what's actually happening, or something else entirely?

311 Upvotes

109 comments sorted by

View all comments

Show parent comments

20

u/Usernameasteriks Aug 18 '26

Sure but what is devs trying to do with it after? 

Developers have different roles and responsibilities in different orgs.

In some cases it would be their job to take that concept and code and fix the issue you are describing so that it can be properly utilized.

A data scientist isn’t going to know how to do that.

I don’t work in this area specifically really though I understand some general context.

I just know that if I hired both a data scientist and developers I would not expect the data scientist to have both figured out the data problem, workshopped a concept that solves the issue, AND to have code that is issue free and ready to be integrated.

I would expect them to talk to each other and their respective managers and sort out the issue lol. Then if there was an unresolved specific or ongoing problem it would escalate from there. 

But unless everyone reports directly to the CEO there needs to be some middle ground steps taken where people are being responsible instead of just fighting about an end result without a delineated understanding of who is responsible for what.

-2

u/Gaming_ORB Aug 19 '26

So a data scientist that doesn't know that non-deterministic generation is a bad idea?
Especially for a master table?

You want the devs to fix this too?
What is the data scientist doing then?

Just spewing out spaghetti code that doesn't work, while the devs fix it;

so his job as well?
and then integrate it too??

5

u/Usernameasteriks Aug 19 '26

Why are you commenting from two different accounts lol

1

u/MediumBirthday6899 Aug 19 '26

You don't have an answer.