Because most of the code you write at a previous job is not going to publicly available. So I have no other reference point as to your current skills.
Apart from just the code itself, having side projects is a good sign of valuable, non-technical skills. Such as intellectual curiosity, ability to start/finish things, and if it's a collaborative open source project, can play well / collaborate with others.
Eh, I’ve never really found that candidates I’ve interviewed with an established open source presence are any better than those without. It does not impress me as an interviewer at all anymore.
Agree. All it tells me is that you either worked at someplace that already open sourced something, or you have lots of time and don’t have hobbies outside of programming.
People think that somehow interviewers or hiring managers are going to dig through some random repo and assess it, but frankly there’s no time nor motivation. The most I’ve ever done is click some links, and see if the repo is just 3 files, or if it’s more substantial. There’s just not any time for anything more, and it’s all going to become clear during the interview anyway.
Every bootcamp teaches it’s students to fake a Github. Unless a person’s repos are substantial original work now, it’s a strong negative signal. It tells me this candidate is trying to game the filters. Which they are.
Apart from just the code itself, having side projects is a good sign of valuable, non-technical skills. Such as intellectual curiosity, ability to start/finish things, and if it's a collaborative open source project, can play well / collaborate with others.