Some days I just can't, I'm fried after work, and then I just hang out with the family.
Some days I just can't, I'm fried after work, and then I just hang out with the family.
Great. Two of the most common hobbies for everyone else is excluded so you have enough time to do side projects (TV here includes streaming service shows, sport broadcasts, etc.). How is this not reinforcing the idea that this purity test excludes many engineers?
Surely the most bias free way to hire would be to say yes to the first applicant. Of course this excludes engineers who are busy and were not able to apply first... so perhaps the randomth applicant gets sent a "youre hired".
I mean. Hey maybe its a better process. We have yet to see some metrics on this.
This is where data would be helpful, and why numerous people have pointed out that bringing code you wrote, IP owned by your previous employer is a no go, and why we've goal post moved instead to bringing in your personal projects.
> If they don't have code to share for whatever reason, like it is owned by their previous employer or they are fresh out of school with no code to show, pass on them.
> You have other code to share?
Data would be helpful, but I don't even know how such data would be gathered. Is there a sure-fire method to identify a "Good Engineer" from one who is not?
I interview occasionally, been working a long time. The numbers of devs I know that have such code to share is small, and I would put them all in the work-with-again bucket. I'm not sure if I would adopt this method, but I've seen worse filters :)