• 2 Posts
  • 109 Comments
Joined 10 months ago
cake
Cake day: August 28th, 2023

help-circle


  • Dandroid@sh.itjust.workstoAsklemmy@lemmy.mldeleted
    link
    fedilink
    arrow-up
    20
    ·
    22 days ago

    I don’t have advice, just a worthless anecdote.

    I work at a large tech company. We had a Windows XP system on our network get hacked. They used that to jump to our servers. IT had to quarantine off the whole lab, because they didn’t know where the hacker had hopped next. So then IT had to do a post-mortem and figure out how they got in and what was affected. That process took 3 months. In the meantime, any team with servers in that lab couldn’t use them. The team directly responsible for this couldn’t work at all for the full 3 months.






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




  • Dandroid@sh.itjust.workstoSelfhosted@lemmy.worldPost your Servernames!
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    2 months ago

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