When it comes to hiring, I'll take a Github commit log over a resume any day.

Post by bphogan » Thu, Mar 31, 2011, 2:42 PM UTC

vgurgov wrote: post #73

bphogan wrote: post #52

Earlier quoted context omitted.

The problem is that I can't believe a word you said. I can't see examples of this awesome super top-secret code because it's all closed-source, as you say, for good reasons. I also can't trust your references, because you'll only give me ones that will say good things about you, and any digging at your work history will only uncover "yes he worked here" responses. I want to see open-source contributions because I lik…

'The problem is that I can't believe a word you said' Thats fair, but the thing is that its YOUR PROBLEM(as a recruiter), not mine as a great "closed source" engineer I know bunch of people who work on very cool and interesting problems/projects binded NDAs and have no problem on finding a new job if they want to. Hell Facebook, twitter, google are all closed source(mostly) so wouldnt you hire ex-Facebook engineer if…

Post by Cymen » Thu, Mar 31, 2011, 4:12 PM UTC

optimusclimb wrote: post #90

Cymen wrote: post #67

Earlier quoted context omitted.

It is becoming increasingly rare to work on an island away from open source. A lot of companies use open source in some way and having an in-house developer familiar with the projects they use or relay on can be quite useful. And the improvements that the company is willing to pay for but aren't a competitive advantage can be committed to the open source project. It's a win for everyone. Do you work on an island?

You people are insane. Going out on a limb here, as I hate making my life public - I worked at Factset Research Systems for just about four years. They are a publicly traded company (FDS - NYSE). Guess what - They would allow precisely 0% of the code I wrote for them while working there to be shown to another company. So what you are saying, is that, given that, unless I went home and coded and contributed to an open…

Post by technomancy » Thu, Mar 31, 2011, 5:15 PM UTC

nwp wrote: post #78

I frequently fork projects on Github, add features/fix bugs, send a pull request and then delete my fork after my changes have been integrated. I've started to consider keeping my forks around for this reason alone but that strikes me as a waste of Github's disk space...

Post by [deleted] » Fri, Apr 01, 2011, 4:38 AM UTC

tomjen3 wrote: post #105

ori_b wrote: post #41

Earlier quoted context omitted.

The hiring process isn't meant to be fair - it's meant to get the best results. A good way to see if someone can write good code is to look at the code they've written and to see if it's good. If the ability to demonstrate that they can write good code with concrete examples puts someone at an advantage over others, so be it.

Actually in this case it puts people who like git over people who like mercurial, svn, rcs, etc which is unlikely to benefit anybody . Last time I heard git sucks on windows, svn is still extremly widely used (try writing a game with a large amount of binary assets and use git) and some of the old open source systems still use CVS.