← Back to context

Comment by Gigachad

5 days ago

At least once a week I have to drop what I'm doing and race in to stop the non dev manager from merging a fully vibe coded patch which will blow up production. Claude Code has made this guy a negative 10x developer.

10 comments

Gigachad

Reply
SwtCyber  5 days ago

Just let him take down prod on a friday night once and leave him to deal with the PagerDuty alerts solo. Cures the urge to vibe-code infrastructure real fast

  • tonyedgecombe  3 days ago

    People like that are usually pretty good at deflecting onto other people. Likely you will end up being blamed in some way.

bwhiting2356  5 days ago

how does this non dev manager have perms to do this

  • Gigachad  5 days ago

    They don't have permissions but if I don't rush to block the PR with a bunch of review comments, one of the other AI brained devs will just hit approve on it without reading or understanding anything.

    Yes it is hell here. But it's a new kind of problem that just showed up.

    • NichoPaolucci  5 days ago

      I'm experiencing similar rubber stamping around my company.

      CEO hired an AI forward CTO / Head of Engineering. He said at his last company his directive was NOT to look at code anymore.

      I've watched thousands of lines of misguided, verbose, brittle code (but there's 24 tests that nobody reads) go essentially straight into production. Nobody understands it, we're adding so much trash documentation that is impossible to keep up with.

      It's an absolute train wreck, I feel farther away from the system than I did when I started. Commit messages / PR descriptions are to be generated by AI (and pushed).

      It's only broken production code a couple of times so far, but my guess is as this continues we will be unable to maintain the codebase without AI involved.

      AI can be a force multiplier, we are not using it that way.

      My main issue with it is that when a human developer broke the production codebase there is generally an "A-Ha" moment, like, "oh no... I know exactly what that error means, let me run a hotfix and we can change things so that doesn't happen again."

      Now we're at the full behest of Claude "do you see what happened to our codebase, robot? Can you help fix it?". Not a fun place to be...

    • eudamoniac  5 days ago

      This is so maddening. I'm tech lead and I run a tight ship on the repo I'm in charge of, all PRs unofficially wait for my approval (it's mostly juniors), but if I ever go on PTO, people just approve absolute shit. It is a common occurrence that I come back from vacation and have to get people to revert merges.