3 ms·
Humm. First, this blog post was not a quick read while taking a quick break to read a hackernews post, so read if you have time. Second, while being able to see
by thehme 13y ago
Humm. First, this blog post was not a quick read while taking a quick break to read a hackernews post, so read if you have time. Second, while being able to see what a developer's programming style and their interests are like via a code repository, not having a code repository does not mean someone is not a good programmer worth hiring. It seems like those who will ONLY hire someone if they have an amazing github are asking for people who do NOTHING but breath, eat, and sleep code; someone without a life, someone who does not cook, have pets, loves someone, or has other interests than being in front of a computer uploading code to github. When you leave home at 7AM to be be at work at 8AM, and work until 5:30PM, and then you get home to cook dinner, feed your pets, clean a little, MAYBE get to the gym, it's already 11PM or midnight. When exactly do these employers think someone has time to do stuff other than work and take care of real-life responsibilities? I mean, yes, programmers could use the weekend and some if not most do, but if moving to another job means having an amazing code repository, this would not be built over one weekend, maybe not even several. There are brilliant programmers out there who simply do NOT have TIME to spend it creating code for employers to see on a code repository site, so requiring one is in fact discriminatory to those programmers who just cannot spend the time adding to the code repository.
I have personally seen how employers think they are so awesome that they will not even consider a programmer for hiring because of lack of a github. All I can see say is that in the case I have seen, all those employers missed out on hiring a great programmer, one who is truly dedicated to work and programming, one who really does live programming while still having and enjoying life.