167
Dealing with YOLO Vibelord colleagues (lemmy.world)
submitted 6 months ago by to c/programming@programming.dev
48 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
[–] 8 points 6 months ago

I had a colleague who pushed a load of half cocked broken nonsense to a repo i was owner of. Blatant emoji comments from AI and all. I just reverted it because I was under a load of pressure to get it out and on ASAP.

He messaged me 6 months later asking me if I "deleted his code". I told him I reverted it because he pushed a load of broken bullshit to main and swanned off for 6 months.

He was like, "oh..." then i realised. This guy doesn't even know what git revert is. Had to explain it.

What the actual fuck.

  • permalink
  • fedilink
  • source
  • parent