News for hackers. Stuff that matters.
Re:The Tech Recruitment Process at Drivy by _asummers on Monday July 03, 2017 @09:30AM (#14688070)
That ignores the class of FOSS people I like to call the "fixers", the ones that will spelunk a code base because they have a problem, find the 10 line fix that fixes their issue and never come back to the project again. Those 10 lines were probably very useful but doesn't show any larger design ability, despite that being a thing the candidate may be very good at, or large enough to garner a gauge on how that person sees code. Also consider the people who have never contributed to open source because they leave their work at the door. This is all your prerogative on how you want to run this, but I was personally put off reading that section, despite having a good idea what you're looking for. out of it
Re:The Tech Recruitment Process at Drivy by marcgg on Monday July 03, 2017 @09:43AM (#14688162)
Yes it's true that it doesn't fit all use cases. However I would see looking at a few of the fixes you're talking about as an interesting technical interview.