3 ms·

There are lots of fake github profiles with tonnes of forks with no code committed. Be careful. You have to look at the code to see if they're good, and you sh

by lhnz 13y ago

There are lots of fake github profiles with tonnes of forks with no code committed. Be careful. You have to look at the code to see if they're good, and you should have a conversation about it to find out their thinking process. I'd always give a coding/architecture/design test before getting them in to interview as this would allow me to see how they solve new problems.

EnderMB 13y ago
It's also worth noting that even good developers might not understand GitHub. I worked with a guy (around 8-10 years experience, and a good senior dev/technical architect) who spoke to me about someone he was interviewing for a mid-level role. He told me that his GitHub profile was great, and that he had a ton of great code and specs that he had written. In fact, he had forked most of this great code, and the only code that was his was a few tutorials from some books he had read to try and learn C# a year or two ago. He wasn't a bad developer by any means. He didn't get the job because we couldn't get the budget to land another dev. However, there's a big difference in perception between a good developer on merit, and someone that has written some commonly used tools.