• 3 Posts
  • 125 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2024

help-circle



  • proton offers functions to windows programs that those programms expect to be there, however those functions might differ from what the program expect, because they might not implemnted be fully or they don’t cause something to happen that would happen with the windows implementation.

    different proton versions might contain fixes for certain games that break other games or simply do things different enough that game x can habdle that but game y not.



  • Inability to settle on the right words: I’ll write something and think that what I wrote could be written better or differently and then I keep on writing and deleting and rephrasing with different words. Thus making very slow progress.

    editing is not writing, don’t edit before you are done writing the first version of your story, and editing gets easier after the first enarmourment for a story has worn off anyway. sounds easier than it is, but the voice in your head telling you that you are writting badly is not your friend and not helping, even if it might be right sometimes.

    Problems with continuity: I might think up a somewhat long plot line. But I have to write the whole thing in one go because if I don’t then my brain will splinter the story into multiple possible story branches when I stop and I am unable to choose the path to follow.

    have a look at the “snowflake method” and learn about various story structures to help plan the beats of your story. if planning far ahead is not your jam jot down some notes for what happens next, or if you can’t decide turn the possibilities into yes/no-questions flip a coin and run with whatever fate decided. in general take notes, can’t trust that brain to produce the same output twice.

    Lose interest in continuing if I take a break: If I stop writing mid way and take a break from writing for an extended period of time, I am unable to find the motivation to resume. Mostly because trying to catchup with the story up to that point feels hard. I have this same tendency with video games as well where I don’t feel like picking up a game after an extended period of absence.

    thats normal, if a story can’t reignite the spark that lead to starting it in the first place, that story won’t be finished. keep it somewhere you see it from time to time, it might call you someday and if it does not that’s fine, most stories are never finished. if you want to finish something badly try to set a deadline you cant easily ignore, i turned short stories into gifts (a long with a ‘real’ gift) sometimes just to have a reason why it must be done on day x. the story was not necessarily for the person i gifted it to, but i needed the pressure.









  • japan has pretty harsh punishmemts for distirbuting “indecent” stuff and thus the industry self censors and turning penises and vaginas into mosaics seems enough to make everybody look the other way.

    so pretty much the same reason you probably won’t see naked breasts in american movies aimed at teens or kids, just with a different view on what’s seen as decent and what not and in which context.







  • knowing where something happens is not knowing what happens and especially not knowing why it happens.

    A big import of data caused a specific datapoint to be inserted twice into the database, but that only happened in our shared testing environment not in our development environment, logs made it clear that we tried to insert something twice into a join table but not why.

    the fix was easy, we can remove the duplicated datapoint from our data before writing it to the database, and we found an edgecase we can handle further upstream so we don’t end up duplicating it in the first place, but why didn’t we run into this issue in dev?

    the data is consumed from a kafka topic with a single partition and read order is allways the same as write order, so our service behaves the same way if the same data is written to the topic everytime, but it turns out the producer does not necessarily write in the same order to the topic given the same input and gaining that understanding was a goose chase with debuggers, logs and combing through code of multiple services written by multiple devs working at multiple companies and thats the true horror of enterprise development jobs, teying to get someone from a different team or even company on the phone who can actually explain something to you with whom you can analyse a bigger part of a system.