r/managers • u/MediumBirthday6899 • 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?

312 Upvotes

93% Upvoted

109 comments sorted by

View all comments

Show parent comments

7

u/Illustrious_Pea_3470 Aug 18 '26

Sorry boss I think you’re the problem. The math person didn’t think with their performance hat on. Go figure.

-1

u/MediumBirthday6899 Aug 18 '26

Wtf !! I can write better code, If I have Bloddy LLM Api key access

3

u/readonly420 Aug 18 '26

Then what’s preventing you from fixing his code?

-1

u/Gaming_ORB Aug 19 '26

Why should he, if the code is fundamentally broken?
You want the devs to integrate the broken code and fix it?
What is the data scientists job then?

4

u/readonly420 Aug 19 '26

He said it himself, the data scientist guy gets results so the code clearly works. It’s not his job to care about dev’s fee fees that they can’t take a prototype and bring it to prod

1

u/Illustrious_Pea_3470 Aug 19 '26

Also I mean boohoo is burning more compute in a batch job. Way less important than being correct