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.
Thanks for the newsflash! It's always great to hear that snarky boomer anachronism. Do you remember how you'd be watching cartoons then suddenly a dramatic interruption, a banner flying across the screen, clarions sounding, and bam! Newsflash! Upon which your parents tell you to hush because "this is important!".
> the majority of working, paid developers do not do any programming outside of their employer's IP.
Dude. Explain that to your recruiter. I'm just a random and we're hanging out talking about transformers then a guy walks into the bar and proclaims, "I am an AI engineer!" Just show me some code already or what are we even talking about when you say you're an AI engineer?
This isn't a moral issue. I'm glad that you (and allegedly majority of developers) are employed and never do anything outside of work. But for the purposes of a conversation, what are you talking about in a field if you have nothing at all to show in public or to your peer group?
> Public code can't be trusted. […] 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.
Code either compiles and runs or it does. The author can either explain it or doesn't understand it.
That's why we would have a conversation: For instance, if I'm hiring (or if I'm being hired), or we're just having a semi-serious conversation about technical stuff, we typically walk each other through something difficult that we solved. We discuss the code we've written and show it. We talk about stuff and that's how we figure out how much we both know about the topic.
Why is this even remotely controversial? ;-) Do you guys never talk to anyone about what you do or what you know? Do you never help friends or colleagues or even acquaintances discuss technical problems at their companies or startups or with their freelance projects? Do you never just discuss technical stuff after having a meal with friends, when you open a laptop and read code? Do you even never write code with friends for fun or to figure out new stuff about novel problems?
> That's one reason why there are skill tests in interviews. And why people ask for, and contact, references.
Thanks for explaining to me how recruiting and employment works. Thankfully I'm an adult who has existed on the planet for some time. I imagine you assume I've never filed a reference letter? But I've also seen reference letters being gamed just like every other reputation system so ...
Anyway, out of curiosity, if you've literally never done anything other than what your employer gave you, how did you even become a programmer? You left college or high-school and walked straight into a job then learned to code there, or what?
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).
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.
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.