News for hackers. Stuff that matters.
Re:Just fucking figure it out by nostrademons on Sunday October 31, 2010 @02:54AM (#1852696)
I think the main reason to "contribute to OSS" is to learn (and demonstrate!) new skills that you would not otherwise be able to learn on the job. Businesses generally are not in the habit of paying people to do something for which there is no business need. So unless you work at Google, you are very unlikely to have an opportunity to build a webserver. Unless you work on the compiler team of a big company (almost all of which require prior experience with compilers), you are unlikely to have an opportunity to build a compiler or interpreter. Unless you work for Google or Bing, you are unlikely to have an opportunity to build a search engine.

But if you contribute to Apache or Lighttpd, you're building a webserver. If you contribute to Python or create your own open-source language, you're building a compiler/interpreter. If you contribute to Lucene, you're building a search engine.

All of these teach you skills that can be very valuable if you start your own company. If you can take your server count down from 27 to 1, that's money that goes straight to your bottom line. If you can spend 3 hours writing a script that fixes a problem throughout your codebase instead of 3 months doing it manually, that's time that you can use to innovate instead. If you can index the contents of the web efficiently, you'll know how to index lots of other things efficiently, and there's bound to be a startup idea in there somewhere.

I don't think "writing some boring glue code for the frameworks our for-profit businesses use" is all that much of a resume boost anyway. Writing Mongrel or Factor or Rails, however...

Re:Just fucking figure it out by patio11 on Sunday October 31, 2010 @03:07AM (#1852714)
Contributing patches to Rails is exactly what I am thinking of when I say this: it is a lot of work, visibility for new contributors is poor, and the main beneficiaries are going to be for-profit businesses. Yet I hear otherwise very savvy people telling unemployed CS grads that they should build up their github profiles by, e.g., doing patches to Rails. That strikes me as an astoundingly poor use of one's time -- you don't have a coding problem, you have a marketing problem. Patches have a very poor ROI for personal marketing.
Re:Just fucking figure it out by nostrademons on Sunday October 31, 2010 @03:26AM (#1852738)
I don't mean contributing patches to Rails, I mean writing Rails. Or contributing features to projects that are viewed as bit more hard-core, eg. Apache or Python, though even there you're often better-off starting a new project than contributing to an existing one.

There seems to be a general cognitive bias in the programming world against maintenance work, which strikes me as a bit dumb because it's both harder and more important than starting new projects. But as long as it exists, I'm going to exploit it, and do high-visibility but useless projects like port Arc to JavaScript or rewrite Tetris in 3 hours instead of contributing patches to JQuery.

Re:Just fucking figure it out by barry-cotter on Sunday October 31, 2010 @06:12AM (#1852988)
>> There seems to be a general cognitive bias in the programming world against maintenance work, which strikes me as a bit dumb because it's both harder and more important than starting new projects.

This is not unique to the programming world. Starting something and finishing it looks a lot more impressive almost evrywhere than making something that exis´ts better. Just think how much more impressive founding yet another non-profit looks on ones cv compared to doubling the projects of an existing one.

Re:Just fucking figure it out by ramanujan on Sunday October 31, 2010 @05:29AM (#1852931)
Hmmm. If someone put on their CV that they got patches into Rails (or another large, popular OSS project) you wouldn't think of that as a pretty big plus?
Re:Just fucking figure it out by nostrademons on Sunday October 31, 2010 @02:37PM (#1853917)
Relative to what? I'd think of it as a big plus compared to a guy who never contributed to anything outside of his immediate job duties. I wouldn't think of it as a big plus compared to someone who started Rails, or who wrote Mongrel, or who founded his own startup, or even someone who worked for Google or PayPal.

I suffer from the same cognitive biases as everyone else. Even though I know intellectually that getting patches into Rails now is probably harder than starting Rails was, I'm still more impressed by the guy who started Rails.