# Coworker got promoted for insane AI shipping speed. He just got suspended, and now I am expected to clean up his undocumented mess for free. — retained record

> Retained reddit record from reddit:SaaS.

Canonical: https://highsignal.app/data/records/84468a513991aac1

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:SaaS)  published 2026-08-12 05:56 ingested 2026-08-12 07:33

[original source ↗](https://www.reddit.com/r/SaaS/comments/1vm5nbs/coworker_got_promoted_for_insane_ai_shipping/)

## retained text



```
<!-- SC_OFF --><div class="md"><p>fudging some identifying details here so i don't dox myself, but this is very real and just ate my entire weekend.</p> <p>i work in product dev at a mid-sized B2B SaaS. i'm not anti-AI at all. i use our approved Copilot seat every day for tests, boilerplate, boring stuff like that. i get the whole point of moving fast.</p> <p>few months ago we hired a new dev. his shipping speed was honestly unreal and management absolutely loved him for it. all we heard about was his 'initiative and end-to-end ownership.' dude built and shipped a custom onboarding portal for enterprise clients in literally three days.</p> <p>and the crazy part is, it actually worked. clients could log in, update their migration status, and it would ping our CS team through Slack webhooks. management basically made him the poster child for our new velocity push and he got promoted pretty much immediately.</p> <p>I did ask some basic questions during our syncs. where is this thing actually getting its data from? is there a staging environment? who reviewed the DB migrations?</p> <p>apparently i was being too cautious and needed to adapt to the new pace.</p> <p>then a major enterprise prospect hit us with a massive security questionnaire before signing, so IT had to audit the onboarding portal to make sure we weren't doing anything stupid with client data. lol.</p> <p>that's when the whole thing came apart.</p> <p>when they pulled me in to look through the logs, i found out he originally used Enter Pro to prototype the onboarding flow. honestly, the prototype itself was solid. probably the cleanest part of the entire project.</p> <p>everything after that was the problem.</p> <p>he stitched together the production setup using raw scripts generated across his personal Copilot and Windsurf accounts. and again, the app worked. that's probably why nobody noticed.</p> <p>but there was basically zero governance around anything.</p> <p>didn't use our local CLI to sync the final state back to git. zero tests. was pasting client DB structures directly into personal AI workspaces without masking anything. API keys for internal tools were sitting in an environment IT had no visibility into. schema changes were happening on the fly with no migration history.</p> <p>so yeah, it worked.</p> <p>nobody could just tell you what the hell was actually running, where it was running, what had changed, or who had access to what.</p> <p>and to be clear, the original prototype wasn't what IT flagged. it was everything he did AFTER that with unapproved personal accounts, unmasked client context, undocumented production changes and credentials that never went through our normal review process.</p> <p>IT flagged the whole project. coworker got suspended pending investigation.</p> <p>except CS already depends on this portal, so we can't exactly just turn it off.</p> <p>management came to me to &quot;stabilize the transition.&quot;</p> <p>which apparently means congratulations, you get to clean up someone else's entire mess for free.</p> <p>now i'm reverse engineering the data flow, rotating keys, figuring out what is actually running in production, writing documentation that should've existed from day one, and trying to get the whole thing into compliance.</p> <p>on top of my actual roadmap work.</p> <p>no title bump. no extra pay. no deadline adjustment.</p> <p>i told them i'll obviously patch the immediate security risks because i'm not going to knowingly leave a security hole sitting there. but i'm not permanently owning this thing unless they formally adjust my scope and deadlines.</p> <p>management says i'm &quot;making a work issue too personal&quot; and that i'm hurting the customers.</p> <p>and this is the part i genuinely don't understand.</p> <p>if AI-assisted shipping speed counts as productivity, why doesn't all the cleanup count too?</p> <p>the testing. the documentation. the security review. the migrations. the compliance work. the hours spent figuring out what someone else did three months ago.</p> <p>you don't get to celebrate the velocity, promote the guy for it, and then pretend all the engineering work he skipped just magically disappears.</p> <p>someone still has to pay that bill.</p> <p>am i being unreasonable for refusing to permanently own this unless they actually adjust my deadlines and scope?</p> <p>because right now i'm just exhausted.</p> </div><!-- SC_ON --> &#32; submitted by &#32; <a href="https://www.reddit.com/user/KramerDwight"> /u/KramerDwight </a> <br /> <span><a href="https://www.reddit.com/r/SaaS/comments/1vm5nbs/coworker_got_promoted_for_insane_ai_shipping/">[link]</a></span> &#32; <span><a href="https://www.reddit.com/r/SaaS/comments/1vm5nbs/coworker_got_promoted_for_insane_ai_shipping/">[comments]</a></span>
```



document fetched 2026-08-12 07:33 · canonical https://reddit.com/r/SaaS/comments/1vm5nbs/coworker_got_promoted_for_insane_ai_shipping
