2 ms·

Newsflash: the majority of working, paid developers do not do any programming outside of their employer's IP. Someone who worked on successful projects that sh

Newsflash: the majority of working, paid developers do not do any programming outside of their employer's IP. Someone who worked on successful projects that shipped and are still out there, they can point you to that. You can buy the app, or device with their embedded code, or use the website or whatever. Not always an option for everyone, or not all the time. That's one reason why there are skill tests in interviews. And why people ask for, and contact, references. Public code can't be trusted. If you make that the yardstick for hiring people, then everyone and his dog will spin up some phony github repo with stuff that can't be confirmed to have been written by them. Goodhart's Law and all that. You have no idea how much help someone had with the code in their github repo, or to what extent it is cribbed from somewhere else. Enter AI into the picture now, too.

noch 2y ago
[flagged]
- kazinator 2y ago
  > The author can either explain it or doesn't understand it. I've never been challenged to explain any of the code my CV points to. I could have made it all up. If they randomly asked about something I have not looked at in a long a while, it could actually look like I don't know it! There is so much of it that I would have to study the code as a full time activity to be able to fluently spout off about any random sample of it. I think I'm going to rearrange my resume to move the free software stuff farther down and maybe shorten it. It could come across as a negative. Some hiring people genuinely don't understand why someone would put in a 40 hour week and then do some more on evenings and weekends. Well, I don't know how many. In my career I heard something along those lines from around two. Not everyone will tell you. > You left college or high-school and walked straight into a job then learned to code there, or what? It doesn't describe me, but does almost everyone I've ever known in the field (other than distant strangers met through online free-software-related channels, who are an obviously biased sample).
  - noch 2y ago
    > If they randomly asked about something I have not looked at in a long a while, it could actually look like I don't know it! Typically the interviewer asks: "Tell me about something you worked on in this list of stuff you provided." An interview isn't designed to trick you into failing random questions. It's to find out what you care about. You choose what to talk about. :-) At least, that's how I engage in conversations. I want you to decide what you want to talk about so that I can get to know you.
cess11 2y ago
When assessing a candidate that didn't come with a reliable recommendation or similar short circuiting I spend a short time chatting to learn a little about their personality, then I ask for code, suggesting they show a public repo where they keep some of their personal stuff. If they can't I give the option to write some code that they like and they think shows off what they can do, usually suggesting to spend half an hour or a couple of hours on it. To me it's an obvious red flag if there is nothing. It's as if talking to a graphics designer or photographer and they're like "no, sorry, I can't show a portfolio, I've only done secretive proprietary work and have never done anything for fun or practice". Those that show me something get to talk about it with me. A casual chat about style, function, possible improvements and so on. Usually when they have nothing to show they also don't put in that half an hour to make something up, or get back with excuses about lack of inspiration or whatever, and that's where I say "thanks, but no thanks, good luck". If you can't easily initiate a git repo and whip something up and send it to me in half an hour you won't be a good fit. It means you aren't fluent and lack in experience. I might consider internship, or a similar position where you mainly do something else, perhaps you're good at managing Linux servers or something but want to learn how to design programs and develop software as well.

noch 2y ago

[flagged]

kazinator 2y ago
> The author can either explain it or doesn't understand it. I've never been challenged to explain any of the code my CV points to. I could have made it all up. If they randomly asked about something I have not looked at in a long a while, it could actually look like I don't know it! There is so much of it that I would have to study the code as a full time activity to be able to fluently spout off about any random sample of it. I think I'm going to rearrange my resume to move the free software stuff farther down and maybe shorten it. It could come across as a negative. Some hiring people genuinely don't understand why someone would put in a 40 hour week and then do some more on evenings and weekends. Well, I don't know how many. In my career I heard something along those lines from around two. Not everyone will tell you. > You left college or high-school and walked straight into a job then learned to code there, or what? It doesn't describe me, but does almost everyone I've ever known in the field (other than distant strangers met through online free-software-related channels, who are an obviously biased sample).
- noch 2y ago
  > If they randomly asked about something I have not looked at in a long a while, it could actually look like I don't know it! Typically the interviewer asks: "Tell me about something you worked on in this list of stuff you provided." An interview isn't designed to trick you into failing random questions. It's to find out what you care about. You choose what to talk about. :-) At least, that's how I engage in conversations. I want you to decide what you want to talk about so that I can get to know you.

cess11 2y ago

When assessing a candidate that didn't come with a reliable recommendation or similar short circuiting I spend a short time chatting to learn a little about their personality, then I ask for code, suggesting they show a public repo where they keep some of their personal stuff. If they can't I give the option to write some code that they like and they think shows off what they can do, usually suggesting to spend half an hour or a couple of hours on it. To me it's an obvious red flag if there is nothing. It's as if talking to a graphics designer or photographer and they're like "no, sorry, I can't show a portfolio, I've only done secretive proprietary work and have never done anything for fun or practice". Those that show me something get to talk about it with me. A casual chat about style, function, possible improvements and so on. Usually when they have nothing to show they also don't put in that half an hour to make something up, or get back with excuses about lack of inspiration or whatever, and that's where I say "thanks, but no thanks, good luck". If you can't easily initiate a git repo and whip something up and send it to me in half an hour you won't be a good fit. It means you aren't fluent and lack in experience. I might consider internship, or a similar position where you mainly do something else, perhaps you're good at managing Linux servers or something but want to learn how to design programs and develop software as well.