4 ms·
I think the author is confusing the search for passion with the search for better information. If you can’t share code from past and current employers, and you
by vonnik 9y ago
I think the author is confusing the search for passion with the search for better information. If you can’t share code from past and current employers, and you don’t believe that your quick and dirty solution during the interview represents your best work, then a side project that shows a little carefully crafted code is one way to give a potential employer better information. And better information derisks hiring decisions. With perfect information, hiring decisiInd make themselves. It’s perfectly fine to prefer art projects to side projects in code, as long as you also accept the informational disadvantage and its repercussions.
- nanodano 9y agoEveryone is responsible for showcasing their skills and selling themselves. People who refuse to do that are only hurting themselves.
- onion2k 9y agoPeople who refuse to do that are only hurting themselves. If an employer passes on candidate for the wrong reason then the employer is hurt as well. A good hiring process shouldn't rule out people for reasons that aren't related to their capability to do what they'll need to do in the job, and very few jobs require a good github profile. It's a useful proxy for development ability and passion, but that's all. You can be an awesome developer and never touch Github.
- jordanpg 9y agoThere seems to be a weird inversion in the minds of many commenters here: that they are somehow entitled to dictate the terms under which they are selected to work somewhere. Isn't the point that if you want the job, you do whatever it takes? Why are we not celebrating the fact that we work in a kind of meritocracy where it really is possible to showcase your skills without any credentials or reference to your past? All of this bloviating about "wasted time" in the context of demonstrating skills reeks of bitterness from lost opportunities to me.