Programming

26022 readers

412 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

143

Dealing with YOLO Vibelord colleagues (lemmy.world)

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

39 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

[–] MonkderVierte@lemmy.zip 5 points 1 day ago* (last edited 1 day ago) (2 children)

You render diffs in the browser?

And no, let the yolo fix the things he broke, or he will never learn to be a responsible coder.

[–] eager_eagle@lemmy.world 4 points 5 hours ago

browsers are quite capable of rendering text, even images!

[–] jtrek@startrek.website 14 points 1 day ago

GitHub and similar tools show PR diffs in the browser.