3 ms·
I know nothing about the entertainment industry, but this idea of 'putting in your dues' by working your way up from a menial position based on personal relatio
by patio11 16y ago
I know nothing about the entertainment industry, but this idea of 'putting in your dues' by working your way up from a menial position based on personal relationships has always seemed naive.
I get very, very worried when I see "contribute to OSS" as career advice, for exactly this reason. No, we won't pay you, but if you could grind out some boring glue code for the frameworks that our for-profit businesses use to make money, that would be great. Why, if it turns out that you're good at it, we might even look upon that favorably in an interview... some day.
- nostrademons 16y agoI 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...
- patio11 16y agoContributing 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.
- nostrademons 16y agoI 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.
- barry-cotter 16y ago>> 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.
- ramanujan 16y agoHmmm. 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?
- bphogan 16y agoI don't want to hire people who "paid their dues" but I do want to hire passionate people, and those that contribute to OSS seem to be the ones actually interested in programming, and that gives them a higher chance of getting along with me and others. Someone can tell me all sorts of accomplishments on their resume. They can tell me about some cool NDA or Intranet project they wrote lots of code for. But I can learn a LOT more about their skills from their Github page. So when I tell students to get into OSS, it's not to get free labor or to make them "pay their dues". It's to give them a better shot.
- ZeroGravitas 16y agoYou could say the same about getting a degree, and you actually pay for the privilege in that case. But in both cases it's an okay signal that you're not going to be a total loss, which gives you a leg up on all the other folk who haven't proved anything about their worth (even if they're actually better than you). In theory the more qualified you are the easier it is for you to meet these goals. It also sounds, with they way you put it, that it's the leaders of Project X, telling you to contribute to Project X in order to be hired by the leaders of Project X. Which is, or would be, scummy but I've never seen that advice. Usually it's leaders of project A saying that you should contribute to X, Y or Z because when they or similarly tech savvy people are hiring they'll consider that a good signal, all the more so if it's a project related to your work).
- rmc 16y agoContribute to OSS is good for your CV as a way to separate you from the loads of CS graduates who are not passionate about programming. There are people who have CS degrees who can't programme. If you have contributed to OSS then you are probably not one of them.