Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)D
Posts
2
Comments
103
Joined
3 yr. ago

  • 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.

  • I have only ever packaged for RPM (the company I work for has our own RPM-based distro). How does it compare? I find RPM to be pretty easy, but I have nothing to compare against.

  • I think soap deserves an honorable mention.

  • Different strokes, I suppose. I have never cared for graphics in a game. I don't care today, I didn't care when I was playing Super Mario World as a kid. I care far more about gameplay, tight controls, and later in life I started caring more about good narrative. The best looking game in the world wouldn't keep my attention if the controls felt like garbage, or if the gameplay was just plain boring.

  • Mine are named after fictional robots, computer programs, or AI. It started with my wifi being GLaDOS for 5 GHz and Wheatley for 2.4 GHz. I thought it was funny that everyone could immediately tell that Wheatley was the slower one. Over time, I continued the trend. My gaming PCs are named after characters from the Mega Man X series (desktop is Zero, laptop is X, steam deck is Sigma). My macs are named EVE and WALL-E. My server is named Sibyl System (from Psycho Pass).

  • I think "you're welcome" is just too formal. I would say it to a customer, not my friend.

  • Most games I like are 2D, so that's kind of a weird statement. I grew up on SNES, though. My family skipped the N64, so I didn't even get a 3D console until the GameCube... Which I didn't even get until years after it launched.

  • I have played both, and I enjoyed both.

  • I am a younger millennial, and I've literally never heard of a boomerang in this context in my life.

  • Poor Gen Xers still don't exist.

  • Korben my man. I-I-I-I have no fire.

  • I think it's fine for kids younger than teenagers. Maybe around 8 and up. By the time they are teenagers, most kids are watching anything and everything, included R-rated movies.

  • I love Linux and KDE Plasma, but my biggest complaint is the inconsistent UIs. Specifically the frames. If I have 5 windows all maximized, and I want to minimize a few of them, the frames could all be different thicknesses, or the minimize, maximize, and close buttons could all be different sizes from the other windows, causing you to need to move your mouse around to minimize each window. On Mac or Windows, you can hover the one spot and spam click, because you know every window will have the minimize button in the exact same spot.

  • From what distance away? Because I had them, and I promise they weren't as loud from normal use distance than a jet engine. Maybe if your ear/microphone is basically touching the bag, but your ear isn't normally that close. Plus, exposure time is pretty significant factor for hearing loss. Rolling up a chip bag once every couple of days when you have chips isn't going to cause hearing loss.

  • It wasn't that loud.

  • My sister stayed at my place when she was in town for an event. At one point I heard her alarm going off for an hour before stopping. She woke up an hour later and was like, "my alarm never went off! I'm so late!"

  • At the time, I thought the Sun chips bag situation was hilarious. If I think back on it now, it's really sad. Yes, the bag was significantly louder than the original bag. But I feel like we're going to need to make some sacrifices as a society for the environment. And that seems like a really, really tiny sacrifice.

  • When I was like 13 and was learning to play guitar, I learned sooo many songs by Avenged Sevenfold. And then I saw pictures of them playing concerts with the confederate flag, and even had custom confederate flag guitars. I lived a pretty sheltered life and didn't quite understand how big of a deal that was at the time, but it definitely felt a little gross to me. I slowly stopped listening to them.

    They did eventually come out and say that they regret doing that, for what it's worth. But I never went back to listening to them.