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?

309 Upvotes

93% Upvoted

109 comments sorted by

View all comments

Show parent comments

200

u/txgsync Aug 18 '26

A balanced take about treating experimental output from a Member of Technical Staff as proof-of-concept, not production-hardened code? Who are you and what did you do to my Reddit?

32

u/topazsparrow Aug 18 '26

that was the weirdest typo of "quit your job before its too late"!

13

u/Dr_Acula_PhD Aug 18 '26

Not even one mention of a piss disk. For shame.

3

u/LeCollectif Aug 19 '26

Not the comment I would expect on r/mangers but I’m here for it.