Programming

26022 readers

279 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

130

Dealing with YOLO Vibelord colleagues (lemmy.world)

submitted 1 day ago by reabsorbthelight@lemmy.world to c/programming@programming.dev

36 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] Shayeta@feddit.org 8 points 17 hours ago (2 children)

By that logic wouldn't you be firing the vibe coder for not rolling back the commit?

[–] Simulation6@sopuli.xyz 5 points 16 hours ago

Fallback and fix is the best solution.

[–] xav@programming.dev 3 points 15 hours ago

Maybe. Context is not sufficient (mistakes can happen, intention counts) but breaking prod may be bad depending on the product type.