this post was submitted on 11 Mar 2026
106 points (97.3% liked)

Programming

26036 readers
148 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

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
106
Dealing with YOLO Vibelord colleagues (lemmy.world)
submitted 3 days ago by reabsorbthelight@lemmy.world to c/programming@programming.dev
47 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
[โ€“] eager_eagle@lemmy.world 1 points 22 hours ago* (last edited 22 hours ago) (1 children)

So does a browser. Modern browsers don't even need to receive the whole HTML to start rendering things.

There's a lot of engineering effort put into browsers, much more than in terminal emulators because they need to do much more than just rendering text.

[โ€“] MonkderVierte@lemmy.zip 1 points 21 hours ago

Ok, maybe i have a slight bias, because editors in-browser are usually a system-in-system(-in-system) JS mess.