• 1 Post
  • 87 Comments
Joined 1 year ago
cake
Cake day: August 28th, 2023

help-circle


  • Maga Man X on the SNES. I still vividly remember the first time I ever beat a boss in it, too. I remember running out of my room to look down the loft to the living room area and screamed to my mom that I finally beat Chill Penguin. She wasn’t impressed. I immediately went back to my room and beat another boss. Then another. After probably a couple of years of just dying over and over, something clicked that day, and I was able to beat all the bosses. And I have been hooked on gaming ever since.










  • It’s a 2021 Asus Zephyrus G15 with an AMD CPU and an Nvidia GPU. I got an aftermarket SSD off of Amazon so I could dual boot with Windows, but I haven’t booted back into Windows a single time since installing Linux. Though that might be a good test.

    I can try set -x once I reinstall my distro and get it back up and running tomorrow, as it is currently borked. Since zypper does all the downloads then all of the installs, I was able to see that it always happened during the install phase, not the download phase.

    I am definitely interested in the possibility of it being related to the proprietary Nvidia driver. When it happened yesterday, the proprietary Nvidia driver was being updated (not sure at that exact time. But it was in the list of packages to be updated). I’ll keep an eye on that for sure.


    1. Already done. :)
    2. It started with GUI, but I switched to command line, and even did it in a separate TTY to make sure it wasn’t something weird going on with updating plasma from plasma. After switching to Arch-based distros, I have only use CLI.
    3. Currently I’m on EndeavourOS, but after the most recent time this happened, it won’t boot, and I can’t even mount and chroot to it (I get an I/O error message)
    4. No, I’m at about 1% capacity.
    5. I ran this from a live USB, and it came back with no errors detected, but returned instantaneously, so I’m not sure if it ran the right thing. Doing more research on it now. Edit: I did it wrong. The test is running now. Edit 2: Smart says it passed. :/





  • The 20% is relatively new. It was always around 10%, and then restaurants started “suggesting” higher tips on the receipts, and basically guilting people into tipping more. It was pushed up to 15% in the mid '00s, and then only pushed up to 20% during Covid. I have been called a piece of shit human on multiple occasions because I didn’t buy into the restaurants randomly changing it on me. There is immense social pressure here around tipping.

    The restaurants have a financial motivation to want the tips to be higher, so I feel like it’s a conflict of interest for them to be suggesting the tip amount. I think the government needs to get involved and regulate tipping or even outright ban it at this point, because restaurants aren’t going to stop pushing the envelope at 20%.



  • I imagine people who care about this sort of thing are more likely to report it. And people who care about this sort of thing are also more likely to be early adopters and go through the effort of switching to Wayland.

    The way to get a more random sample is not something I want (built-in, automatic telemetry by default). So I’m fine with having skewed data for something like this.


  • I conducted coding interviews for a few years at a startup before moving to a bigger company where I had a smaller role.

    For me, I never cared about if someone got the right answer. I have actually said no to people who got the right answer and yes to people who got the wrong answer (or didn’t finish). The purpose of the interview is to see if I want to work with that person. If someone can write a perfect program, but can’t tell me why it works, that gives me no insight into how they solve problems or if they even know how to solve problems. What I want to hear is their thought process.

    First repeat the question, and emphasize the key details. Speak an example input and output of the function so the interviewer (and you!) knows you understand the problem. Then start talking about what kind of algorithms or data structures you might use to solve this problem. Reference other common problems that might be similar, and how they differ. Specify patterns that could be used for this problem or even your comparison problem, and whether or not that will work for this one.

    Doing all of these steps with spoken words helps your interviewer understand how you think, and they may give away hints to mistakes in your thought process, or even point out that you are misunderstanding the question entirely. And that’s okay! It’s better to work out the details when speaking about it before writing any code.

    Treat the interview like you are solving a problem with a colleage in pair programming. Bounce ideas off them and see what they think. They are very likely to give hints if you talk to them in this way. If you are stuck, tell them! They might be able to reword a part of the question to help you think about the problem in a different way, leading you towards the solution.

    AFTER you and the interviewer are both confident that you understand the problem, and you have discussed all the algorithms, data structures, patterns, etc. that you need, maybe spoken through a some pseudocode, or maybe written down a table of example inputs and outputs, only then start coding.