3 ms·
It's all about context. While a candidate might have some code online, you save a lot of time by having some code that you're more familiar with and can utilize
by hkarthik 15y ago
It's all about context. While a candidate might have some code online, you save a lot of time by having some code that you're more familiar with and can utilize to see how they think about a problem.
Also it's good to see how someone reacts to digging around in an unfamiliar code base and see how they familiarize themselves.
- assaf_lavie 15y agoContext is true. It's totally different to see someone work _with you_ on a project than to rummage around their commits to project you don't really know. The point is to see how it is to collaborate with someone, and that has to be a first-person experience (or take the word of someone you really value, but that's not what you get form random GitHub projects). And also there are tons of developers who never really contributed much to open source. e.g. in the Microsoft world this is not so rare, and you'll miss these people if you _require_ a GitHub reference...