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
[–] 1 point 6 months ago* (3 children)

Not true. Browsers are definitely faster handling text than your average terminal emulator without GPU capabilities, they just use more resources.

That said, GitHub diff viewer specifically is a sluggish mess. But that's not because of the browser.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 6 months ago* (last edited 6 months ago) (2 children)

    What, you think the usual text editor renders all lines just because? No, they load the lines that are currently visible + some more for scrolling. At least the ones that don't choke on a mere 100k lines. And they don't need GPU for this.

    But webbrowser engines just aren't made for this, but for DOM rendering.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 6 months ago* (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •