News for hackers. Stuff that matters.

A comment on The GitHub Job Interview. Parent comment

Re:The GitHub Job Interview by rhizome on Sunday January 08, 2012 @11:43AM (#3439883)
Why go through all this complication? Use bugs that have actually occurred in your app, repurpose those into coding problems, and see how the prospect solves it. You might be surprised that they fix the bug better than your existing employees (or you).
[ Parent | on HN ]
Re:The GitHub Job Interview by teyc on Sunday January 08, 2012 @03:41PM (#3440448)
Production code baes are never trivial enough for a quick test. They usually require a deep understanding of domain.

Have you ever tried to fix an open bug on a GitHub project? It is non-trivial.

[ Parent | on HN ]
Re:The GitHub Job Interview by rhizome on Sunday January 08, 2012 @05:12PM (#3440669)
Well you don't give them the entire codebase, you package the bug-that-was-fixed into a tiny example app. I think it probably goes without saying to exclude changes in business rules.

Is this not closer to the actual job than Pascal's Triangle?

[ Parent | on HN ]
Re:The GitHub Job Interview by teyc on Sunday January 08, 2012 @07:32PM (#3441015)
oh I see. I agree with you entirely.
[ Parent | on HN ]