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.

  • not_woody_shaw@lemmy.world
    link
    fedilink
    English
    arrow-up
    16
    ·
    edit-2
    1 day ago

    Changes that big need to be broken down into smaller PR-sized steps. To do that you need an actual plan of how to get from here to there. Bro is swaggering like a senior then coding like a junior.

    What to do? Well now you have evidence that AI tools are not yet good enough to write code that doesn’t need human review before deploying to prod. Chat with whoever is in charge of Process, and get some team guidelines in place to prevent unreviewed code going to prod, and unreviewable PR’s being submitted for review.