That's the important thing. Sometimes the initial excitement of seeing that github account wanes when you realize 8 projects are forks of existing projects with one change, and the other two are a stock rails project with only three or four minor commits on top of that.
I'd generalised it from another webapp I was buildingfor someone else (that didn't pay) summer last year.
https://github.com/dublinclontarf/SchoolOut
This is pretty much some of the only code I've made available in public. Should I put up the entire webapp that I built during the summer? It's not doing anything.
I'm hoping to finally launch the private beta this weekend, there are still some invites left. You can sign up for one if you like at:
It has some other cool stuff like auto PDF generation and private cover letters/videos.
One of the things that held me back though was that I wanted the projects to be "ready." To get them to a point where I can show them off instead of having several abandoned and "poorly written" projects. (Quoted because you really are your own worst critic.)
I now think it's much better to show you can ship on your ideas. To build, publish, and move on to your next idea. It's a much stronger indication of your passion for programming than words alone. Saying "I like to hack in my spare time" without further evidence just doesn't have much impact.
Does anybody disagree? Are there cases where publishing imperfect code and abandoned projects alongside your best was a disadvantage to you?
It didn't seem to be helping, however it turned out that most recruiters were scrubbing it from the version they passed on to prospective clients.
So after my break, I honestly listed that as 'funemployment' on the resume, with a brief human understandable explanation. (I actually was working on some of my own non-programming related projects, and explained as much.) In the email cover letter, I basically said "Here's my resume, but I think my website does a better job of explaining my real strengths as a developer."
An interesting thing happened. Without exception, any company with an HR department totally blew me off. And without exception, any company where the owner screened the resumes, I got a phone screen and a real interview.
I also think that's something where having a custom domain for your email really helps. If any tech-savvy person gets a resume from [email protected], they're pretty much going to instantly open up a browser and type http://not-gmail-or-yahoo.com.
That it's populated with tiny little projects that only work exactly for what they were intended, didn't seem to be much of a deterrent to anybody.
Yes, yes, a billion times yes!!!!!
Even if it's some tiny little project that went nowhere, the fact that you actually have some code that is yours and that you can discuss intelligently puts you well ahead of 99% of the people I see.