News for hackers. Stuff that matters.
Re:Coding Interview Tips by Zombieball on Wednesday October 16, 2013 @02:39PM (#6561326)
In fact some companies explicitly prohibit publishing code publicly without requesting special permission.

I don't think candidates should be excluded based on the lack of a github repo.

Re:Coding Interview Tips by freework on Wednesday October 16, 2013 @02:56PM (#6561418)
Its no that difficult to create a github project that can be completed in a weekend. I created the hacker new karma tracker and weedprices.biz in one weekend each.
Re:Coding Interview Tips by adamnemecek on Wednesday October 16, 2013 @03:06PM (#6561474)
But would you really make hiring decisions based on either of those projects? Software development is 'relatively' easy when your project is <1000 LOC. It becomes harder as the project grows. And it's the ability to grow the project what you should make the hiring decisions on.
Re:Coding Interview Tips by mattstreet on Wednesday October 16, 2013 @03:57PM (#6561784)
Yeah but judging someone's ability to code by several good <1000LOC projects is probably better than the sorts of coding problems you have time to give someone during a coding interview.
Re:Coding Interview Tips by adamnemecek on Wednesday October 16, 2013 @04:19PM (#6561912)
That's actually a good point I have not though of before. I considered your Github account to be the place where you'd show off your l33t sk1llz, as opposed to show off code similar to the code you'd write during interviews.
Re:Coding Interview Tips by nephorider on Wednesday October 16, 2013 @04:01PM (#6561803)
Sure but then if this becomes a "must have simply to have the opportunity to interview" then it loses all the value it can have to reveal what the person can do. And I do believe some people have no time for this. Having worked at Apple for some time, I guarantee my sparse time, when there was some, was more outside of any coding and still I will never show outside a piece of code I have written in this company. This does not mean the coding skills I have should be considered as good or sufficient, they may or not match the one needed for a position. Having been also in the position to be on the interviewer side, especially in startup, seeing the candidate in person reminds often the deciding point.If some code on github exists, it simply can "speed up" a little this part of the process. Personally I found the "Smart and get things done" book by Spolsky a good read on how to conduct interviews
Re:Coding Interview Tips by mnbvcxza on Wednesday October 16, 2013 @07:00PM (#6562618)
And I could copy them with minor modifications and claim I designed it all, in only a few minutes.
Re:Coding Interview Tips by toomuchtodo on Wednesday October 16, 2013 @03:07PM (#6561485)
I agree, but I understand its part of the game played. I have 13 years of IT experience, but still contribute to open source projects on Github, as my day job codebase can't be released/be part of my portfolio.
Re:Coding Interview Tips by vonmoltke on Wednesday October 16, 2013 @03:51PM (#6561756)
As soon as things like that become "part of the game" they start losing their signalling value.
Re:Coding Interview Tips by hackinthebochs on Wednesday October 16, 2013 @05:36PM (#6562286)
Exactly why I cringe at every one of these "my awesome interview tips/tricks/hacks/etc". The very fact that you publicly stated it makes it lose significant value. Most forms of testing are high value until the test becomes the goal, then its worthless. I guess having a handful of hits on their block one afternoon is more valuable to them than a useful hiring signal.