3 ms·

Or what about having a repository proving these very concepts with almost 2000 commits? In my experience things like publications, online code repositories, an

Or what about having a repository proving these very concepts with almost 2000 commits? In my experience things like publications, online code repositories, and facts are more than irrelevant but not much more because people don’t know how to independently evaluate these things. Worse, attempting to evaluate such only exposes the insecurity of people not qualified to be there in the first place. Far more important are numbers of NPM downloads and GitHub stars. Popularity is an external validation any idiot can understand. But popularity is also something that you can bullshit, so just play it safe treat everyone as a junior developer and leet code them out of consideration.

jstx1 3y ago
It's easy to fake projects and commits. And when they aren't faked, you can't have an expectation of every candidate having these because it's so much work. And if you decide to bypass some of your usual interview process because a candidate has a project, now you aren't assessing all candidates equally.
- austin-cheney 3y ago
  All I see from your comment is that candidate evaluation requires too much effort, so you exchange one bias for another.
  - jstx1 3y ago
    It's a choice to treat all candidates equally. And intentionally excluding candidates is the whole point of designing an interview process, it's lazy to lift your arms up and declare that they're all biased.
  - yencabulator 3y ago
    I've interviewed people for roles as low-level C++/kernel programmers who did not know what hexadecimal was. Having a quick "What's 0x2A in decimal? Feel free to use paper & pen."[1] question can be a significant time-saver / direct people to more appropriate roles, if any. [1] Starting to do math with non-base-10 numbers was already a pass, regardless of the number you reach, you'd normally use a computer for that. But it really isn't too hard to do in your head directly, for anyone who's dealt with binary data.
    - austin-cheney 3y ago
      I am not sure how that has anything to do with what I posted.

jstx1 3y ago

It's easy to fake projects and commits. And when they aren't faked, you can't have an expectation of every candidate having these because it's so much work. And if you decide to bypass some of your usual interview process because a candidate has a project, now you aren't assessing all candidates equally.

austin-cheney 3y ago
All I see from your comment is that candidate evaluation requires too much effort, so you exchange one bias for another.
- jstx1 3y ago
  It's a choice to treat all candidates equally. And intentionally excluding candidates is the whole point of designing an interview process, it's lazy to lift your arms up and declare that they're all biased.
- yencabulator 3y ago
  I've interviewed people for roles as low-level C++/kernel programmers who did not know what hexadecimal was. Having a quick "What's 0x2A in decimal? Feel free to use paper & pen."[1] question can be a significant time-saver / direct people to more appropriate roles, if any. [1] Starting to do math with non-base-10 numbers was already a pass, regardless of the number you reach, you'd normally use a computer for that. But it really isn't too hard to do in your head directly, for anyone who's dealt with binary data.
  - austin-cheney 3y ago
    I am not sure how that has anything to do with what I posted.