So my manager today asked me if I could stay later when there’s broken things in prod, and then today his star dream employee yolo’ed a full stack change into prod without review. It’s fucking massive and implements new API endpoints, touches >20 files. Many of the diffs are too large to render in the browser.

It’s almost comical, but something immediately broke.

Most of my day, I’m digging through code to identify bugs created from this shit, just to get a stealth merge midday.

I kind of don’t know what to do.

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    100
    ·
    2 months ago

    I would say no to staying back. The employee that broke it needs to fix his code, at the very least roll the change back.

    At the next meeting or post mortem bring up why code can be pushed to prod without review. Your git forge should be able to block merging to prod by a single person.

    • reabsorbthelight@lemmy.worldOP
      link
      fedilink
      arrow-up
      37
      ·
      2 months ago

      Yeah. I log off at EOD and don’t check messages. It’s not my families fault he lets his employees vibecode shit into prod. The Vibelord is the main problem, but others do similarly stupid things.