Huh?

  • 0 Posts
  • 20 Comments
Joined 7 months ago
cake
Cake day: June 8th, 2025

help-circle








  • *data engineer

    I’m also one but I don’t work for advertising. Most data engineers work for consulting companies that work for banks. We program automatic data processing pipelines. For example, bank transactions are stored somewhere, all the historic data, that needs processing to then be graphed out for exec number 3, or for whatever.

    Other companies might send you files that need to be automatically processed, cleaned, and put correctly where then other tools can pull that data correctly.

    We basically do all the background work concerning data manipulation. File processing, databases… all that stuff. And by databases it can be normal ones like posture to distributed ones like hdfs/hive/athena/whatever.

    Ad world is basically the same but with tracking info instead of transactions.

    If you are interested in day to day work, it’s a mix of coding SQL processes, then porting them to spark/pyspark for distributed massive processing. There are new shiny tools for those that don’t know much of the technical side to manage, sorta.



  • you didn’t understand. I know how the bug worked and was spread, using unsummoned pets and all. What I said is that it’s wild to me that they didn’t change the debuff to be unable to be spread at all for like a day. Like, change how the debuff spread works to temporarily disable it.

    Doing a check each time the buff spreads is inefficient use of server.

    WOW is server authoritative, meaning that who gets the debuff is decide by the server each time, doing a location check shouldn’t be that inneficient, the character object should have a cheap way to get the location it is in, including the name of the area, cheaply. IDK how the game is coded obviously, but that check should NOT be something expensive.

    changing anything about the spell requires servers to be shut down

    Are you sure they had no way to do hotfixes without server shutdowns? That’s been a thing for a while now.






  • The famous bad flicker or ghosting of frames is a famous issue in Wayland caused by the desynchronization of frames. Around 2 years ago they patched the driver to let the system tell it explicitly how to sync the frames, and most Linux systems should have the drivers updated to work as such. Since them I’ve not had any flickering like that. A great example was Dragons Dogma 2, the flickering was insane but fixed by the patch.

    I’ve been in Wayland since KDE 6.0 and I’ve a 3080. I think that’s like 2 years now. And I game A LOT.