I spend a lot longer than candidates do on themselves if they have open source (or if an internal transfer, internal) code I can review.

50% that I’m terrified of bad hires, 50% I recognize the opportunity and gravity from their side so try to respect that.

▲

at-fates-hands 6 days ago | parent [-]

>> if they have open source (or if an internal transfer, internal) code I can review.

I give you a lot of credit for doing this. When I was still in development, I had a pretty robust github page, a sizable portfolio of stuff I had built and other side projects I was working on with various other platforms like Salesforce.

Not once did an interviewer review any of that. I would find myself referring to my github page several times over during the interview. I got so frustrated with interviewers asking me how to do simple things in interviews, I finally walked out of several and told them if they had just taken five minutes and looked at any of my github projects, they would've saved themselves a lot of time asking stupid questions about basic stuff.

▲

sgerenser 6 days ago | parent [-]

Unfortunately, most people’s GitHub accounts are just a smattering of forked repos with maybe one or two (or no) commits done by them. Unless you look closely, it would be easy to be fooled by the average candidates github that is essentially meaningless.

	▲	RugnirViking 6 days ago \| parent [-]
		then don't hire most people? idk, I really can't imagine hiring someone that not only had such a github profile, but saw fit to send it to the interviewer look for repos that aren't forked, especially one that doesn't have all or most of its code committed in a single commit (i.e. forked with extra steps)