2 ms·
My takeaway is that it's more a mark against someone who doesn't want to do their job function in their non-working times as well. To me, not wanting to code ou
by deadmetheny 9y ago
My takeaway is that it's more a mark against someone who doesn't want to do their job function in their non-working times as well. To me, not wanting to code outside of work if you're coding all day is perfectly reasonable and shouldn't count against you during an interview process, an expectation that you have side projects just feels unreasonable. There's obviously not gonna be anything wrong with someone who also likes to code their own projects outside of work for fun. That's my view from the outside as a non-dev, anyway.
- lightbyte 9y agoThat wasn't the argument though, the argument was it "discriminates against people with lives". That's an offensively wrong argument. If the argument was that it discriminates against people who don't hobby program, than yes I'd say that's correct.
- astura 9y agoThere's some subtext you missed there. "it discriminates against people with lives [outside of programming/tech/work]." as in "It should be ok, if you want to, to not spend all your time outside of work doing unpaid work." Excluding candidates that don't have a github or whatever is a signal you are looking to get employees that you expect to spend their entire lives at work. If hobbying programming is your strength, own it. Nobody is going to disregard code samples you send them. The context is employers requiring hobby programming.