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/)TS
thanks_shakey_snake @ thanks_shakey_snake @lemmy.ca
Posts
4
Comments
687
Joined
2 yr. ago

  • Water. Earth. Fire. Air. My grandmother used to tell me stories about the old days, a time of peace when the Avatar kept balance between the Water Goths, Earth Goths, Fire Goths, and Air Goths. But that all changed when the Fire Goths attacked.

  • Now that Wendy's is dabbling in surge pricing these lime-headset-wearing burger brokers are going to become the norm. Rushing to buy your lunch from the nearest shark-eyed capitalist middleman to avoid the noon price spike is the unfortunate dystopian future that our children will grow up in.

  • Design in your head a cabinet that can be designed and built within 30 minutes with no research or preparation, and build it. We will be watching over your shoulder, so please coherently describe your process as you figure out what it is.

    You wouldn't have learned to do this at any previous workshop, so hopefully you've specifically practiced making this kind of shitty half-hour cabinet in preparation.

  • That sounds like a good plan in many situations... But how do you handle candidates who say something like "look, there's heaps of code that I'm proud of and would love to walk you through, but it's all work I've done for past companies and don't have access (or the legal right) to show you?"

    You might just say "well the ideal candidate has meaningful projects outside of work," and just eliminate the others... But it seems like you'd lose out on many otherwise great candidates that way.

  • Pretty questionable take IMO:

    The truth is, there are typically a bunch of good candidates that apply for a job. There are also not-so-great candidates. As long as a company hires one of the good ones, they don't really care if they lose all the rest of the good ones. They just need to make sure they don't hire one of the no-so-great ones.

    That's actually a pretty bad thing. Like you could say the same thing about rejecting applicants who didn't go to a certain set of schools, or submit a non-PDF resume, or who claims to have experince with a library/language that you don't like (I had a colleague who said that he'd reject anyone with significant PHP experience because they probably learned "bad habits") or any number of arbitrary filters.

    If "good at leetcode" was a decent proxy for "knows how to build and scale accessible web UIs" or whatever, then okay great... But it's not, as the author admits in the conclusion:

    Coding interviews are far from perfect. They're a terrible simulation of actual working conditions. They favor individuals who have time to do the prep work (e.g., grind leetcode). They're subject to myriad biases of the interviewer. But there's a reason companies still use them: they're effective in minimizing hiring risk for the company. And to them, that's the ball game.

    So it's unclear to me what they mean by "effective." Are they good at evaluating how good a candidate will be at the job? No. Are they good at identifying talent that hiring teams might otherwise overlook? No. They are good at "minimizing hiring risk" by setting up another arbitrary hoop to jump through.

    Let's just call a spade a spade and admit that our hiring processes are so bad at evaluating talent that we settle for making candidates "audition" to prove that they can code at all, and then decide based on whatever entrenched biases we've decided constitute "culture fit." Then the title could be "Coding interviews are the most effective tool we have, and that's kind of a disaster."

    Thank you for reading my rant. I am available for podcasts and motivational speaking appearances.

  • Oh, that's too bad. There are band-style or hook-style versions that could maybe help with that, but yeah most of them are buds.

    One thing I'll say is that when I used to wear wired buds, they would fall out all the time and I thought I just had weird-shaped ears or something... But when I got into wireless buds, I tried out a bunch of styles and found that without the cord, they stay in way more reliably. Wired ones would fall out when I turn my head or just walk 10 steps, but with wireless ones, I can shake my head or run or anything, and they stay in. I guess the weight/movement of the cord makes a big difference, at least for me.