Agree mostly, but I do take issue with the idea that "an active GitHub account should be enough for most programming jobs." Recruiter or otherwise, that kind of assumption is a good way to miss out on talent.
At my current job I have a very active github account - but about 95% of that activity is in private repos.
I am just now starting to work more on contributing to github hosted OSS Projects but -- when I even had time previously -- those projects were often not hosted on github.
For my personal projects, I use my own git repos over ssh. I probably will decide to put them on github when and if I am ready to share them -- but that's not a given.
In my previous job, we didn't use github. Everything was closed source and internal.
Just because one service is the current fad (and don't get me wrong, I generally think github kicks ass) doesn't mean it's valid to assume that your next candidate is using it.
I think what the OP is arguing is that if he has an active github profile:
1. the recruiter should have done the work to check that out before emailing him.
2. his/her profile should be enough to warrant arranging a meeting/interview, and a resume would add little extra information.
If you don't have an active public place where your work is showcased, then certainly a resume is a good (more) private way to provide a potential employer your skillset. Though certainly not the only other way.
I also take issue with the idea that "an active GitHub account should be enough for most programming jobs" but for different reasons. Good programmers do more than just 'programming' or 'coding to a spec'.
What industry verticals has the programmer worked in? A good programmer can add valuable domain expertise and they know the right questions to ask. How have they contributed to the businesses and products they have worked on? To what extent have they mentored and led other programmers? Have they got non-programming experience that could be potentially useful? What methodologies are they experienced with?
At my current job I have a very active github account - but about 95% of that activity is in private repos.
I am just now starting to work more on contributing to github hosted OSS Projects but -- when I even had time previously -- those projects were often not hosted on github.
For my personal projects, I use my own git repos over ssh. I probably will decide to put them on github when and if I am ready to share them -- but that's not a given.
In my previous job, we didn't use github. Everything was closed source and internal.
Just because one service is the current fad (and don't get me wrong, I generally think github kicks ass) doesn't mean it's valid to assume that your next candidate is using it.