Personal time commitments are understandable, but I feel like they are just an excuse in 90% of the cases. As 37signals puts it, "No time is no excuse". If you are serious about improving your abilities and buy into the craftmanship model at all, you can surely find a few hours of month to work on something, anything. Trade an hour of TV watching for an hour of writing your own blog engine or a Todo list app. Or write something to improve some small bit of your life (a program that emails you once a month to remind you to take your SO out for a nice dinner), put that on github. Don't make it out like you have to write the next Rails or jQuery to put code online.
The rest of your issues are largely related to workplace culture.
If you work at a company that uses any open source code (and I know there are some cases that don't due to federal validation and redtape etc etc), you have probably found a bug at some point. Put in an issue on github - send a pull request if you feel ambitious or if you had to monkeypatch the code for your project anyways. I have a feeling that people that work for closed/IP-hungry companies will go to the same kind of company when they change jobs. And that is fine, for some people software is just a job; but those are not the kind of people that read HN or software blogs anyways.
I know you are probably playing devil's advocate here, but every time someone posts about why developers should have side projects or github accounts, these points all get brought up and it bugs me.
Resumes are for deciding who you're going to interview. If github is the new resume, then you're not going to know about the side projects.
I don't advocate "don't hire if no OSS". I work with smart people that get stuff done and don't have a Github account. That's fine, it's a personal choice how you use your time.
What rubs me the wrong way is when people say "It's unfair to look at Github as the new resume because I don't have enough time to do open source". Like I said originally, I'm sure someone is going to come along and post about how every hour of their day is being used for meaningful activities, but for the majority of people I don't think that's true.
I remember once a new coworker telling me -- on his first day, no less- that he didn't have a computer at home. He was proud of this. He was a new CS graduate, and for him, computers were not an interest, at all. It was just a job. I asked him what he was into, and it was sports, naturally.
I didn't like that, it rubbed me the wrong way. I probably would have given him the thumbs down if I'd been in the hiring loop then.
Turned out he was a good engineer. Better than that, the sport he was into was one I got into as well and we spent a fair bit of time over the years in our off hours far away from any computers.
I work for a bigco that doesn't contribute to open source. I used to work for a bigco that was one of the biggest contributors to open source. I spend spare time working on an reasonably sized open source project, of which I was one of the founders, hosted on, yes, github. I have interesting (to me, atleast) side projects, mostly hardhacks, which I don't necessarily build to share. I do it for fun. Obviously, I read HN.
I never require open source experience when I hire, because my experience in both the 'closed' and 'open' worlds tells me that great scientists and engineers exist in both worlds and using a VCS account as a filter is crude. This is just another facet.
I am biased because I do have a github account and work on side projects for fun, but I think it is worthwhile to point out that if time is what you think your limiting factor is (which was the point that cletus made that I was directly addressing), then maybe you aren't really looking hard enough into how you are using your time.
Others told you, so try to understand their viewpoint: you are projecting your own prejudices about time and open source. Maybe, if you look at the cold, hard numbers, you may agree that 90% of smart programmers don't have a github account. True or false? If true, then your claims need to be revisited.
I am happy to discuss it further if there is some part in particular that you disagree with.
Also this would mean I have to use a particular tool for development (maybe I should be required to only use gcc for my C projects too). A particular tool on a particular site. I like Mercurial. The projects I like to contribute might use Google code. Guess I am going to have a hard time finding a job now.
I did not say anywhere in this thread that Github was a requirement and I don't believe that to be the case. I also assume you read my parent comment in which I addressed the fact that Mercurial-based repository sites and Google Code both achieve the same goal.
You aren't required to do any of those things, but it makes sense that the more quality information about yourself available the better your chance at getting a quality job.
None of the work I invest in myself will be available in any form on github because it simply doesn't fit there in any meaningful sense (unless you want me to upload some sort of .txt book report). I spend my "self-improvement" time on conceptual problems that don't map to github or other repositories in any way. If I want to solve a trivial problem, I assume someone else already has (it's probably on github) and there's no point in me reinventing the wheel. What does me writing another ORM tool tell you except that I'm able to copy someone else's ideas?
When a programmer has an active github account with lots of quality code, hiring manager has an easily verifiable proof of programmer's abilities (or lack of it, if the code is bad).
When a programmer can only talk about papers he read, hiring manager has no way to verify if he actually read those papers and if he understood them.
Reading papers is not worse than programming for professional development but it is worse if you're looking to convince someone to hire you.
Reading papers instead of writing open source code is a valid choice but that's what it is: your choice and it comes with the consequences of not being as attractive for potential employers as people who write high-quality, open source code.
People have a tiny itch and write a tiny program to solve that itch. That's fine - I have nothing against someone doing that. However, to take that tiny program and others like it as more than minor evidence of programming ability is a huge leap of faith that I'm not prepared to accept.
For example: I work with a guy who just released an Android app that is a Starcraft 2 build order trainer. It runs a timer and displays an image of what you should be building in the game at that exact moment (assuming perfect efficiency). The idea is that you plug in the order you want to build units ahead of time, and you're "racing" the timer to become more efficient. Supposedly he has about a hundred downloads, so it's not a huge success but it's also not an abject failure as far as apps go. Here's my problem. It doesn't DO anything.
It doesn't suggest reordering your build to account for obvious problems (e.g. never building a military unit). It doesn't optimize your build to account for obvious parallels (e.g. it won't tell you it's stupid to queue up units for production when you could put your resources to work elsewhere for immediate benefit). It doesn't even track wins/losses that I know of. It basically displays a series of images based on a script that you provide.
I'm sure it's very well written software based on the contributions he makes to our codebase at work, but it doesn't say very much about him except "here's a guy who was able to write one mobile app." He's not bad at coding, but he's really not great at solving ill-defined problems, and that costs him when he's confronted with something new. For example, he spent a week as part of a performance effort writing an aspect to generate timestamps whenever a method was called and when it returned. This sort of thing is commonly known as a profiler, a tool which we had access to from the start and which would have worked fine for our purposes. He didn't know about that, and wasted a week getting AspectJ set up and configured and writing his homegrown profiler while the rest of us were making actual, obvious performance improvements based on data from a real profiler.
Yet, according to popular wisdom on this thread, his SC2 app proves beyond a shadow of a doubt that he is a demonstrably superior developer to someone who doesn't code in their spare time. Most of the apps and hobby programs I'm aware of fall into this category. My point is that a program is a solution to a problem, nothing more. If you're trying to hire someone to solve problems (e.g. an engineer or developer - what have you), a demonstration that this person can solve relatively trivial problems should not be taken as a bell-ringer for engineering talent like it frequently is.
So it's a minimum viable product. That's fine, and if I played SC2 I'd find it useful.
He didn't know about that, and wasted a week getting AspectJ set up and configured while the rest of us were making actual, obvious performance improvements based on data from a real profiler
That tells me nothing about his abilities one way or the other; all it suggests is that your team has communication issues.
How will you demonstrate that in ways that I (or a hiring manager/engineer) can see?
Papers? github(bitbucket, sourceforge) code? applications released? conference presentations?
I can hunt down abstract knowledge all day and bloviate like a master, but in the end, it's all hot air if I can't demonstrate my mastery in a concrete fashion.
The advantage people are seeing is that github provides a public mastery demonstration, as well as a view of your work.
My corporate contributions almost certainly will never leave the purview of the company servers. Ergo, if I ever want to show code samples, I will have to write them at home, on my own time.
Certain others with an odd veneration for Github seem to be saying otherwise (see kfalter's post on another subthread), but they are not a majority.
Having an open source project is another means of visibly showing your enthusiasm, and even skill set. Notice how I don't say actual 'skill'. That is always subject to the eye of the beholder.
By your definition, someone better tell https://github.com/jeresig & https://github.com/zedshaw they're JR developers and should go back to school.
That's gone. And no one cared if the corporate designers didn't have time to create a website. Even if you still have an amazing portfolio (which is the resume for the designer), you better have something online (whether they are personal projects done outside of work, or glimpses of projects done at work).
The paper resume is going away anyway. And then when HR finally gets up with the times, do you really think they are going to say, "Aww, it's ok, we understand you didn't get on Github because you were waiting for us..." No.
HR people hiring designers using their online portfolio is a lagging indicator. And the same will go for HR people hiring developers based on Github.
The overwhelming majority of programmers do not use Github for their projects. I would bet that not even a majority of open-source programmers use Github for their projects.
There are alternatives. Quit thinking yours is the only way. It is not.
- those that use different VCSs?
- people who don't have the time (due to their job or other circumstances) to work on things they can open source?
- people who work at companies that essentially own everything they might do so you can't work on open source? and
- companies where hiring goes through HR who won't know what the hell Github is?
Having work on Github is probably a good idea for college students and recent grads but once people are employed it's value drops off significantly (IMHO). From a hiring perspective, you're also greatly limited your field of candidates if you only look at Github profiles.