What writers don't understand (and what they'll rarely be told) is that paying your dues is largely a process of disillusionment. To put it kindly, the industry wants sensible, informed writers who understand how TV is made and know how to write scripts that are easy to shoot and suit the medium. To put it less kindly but more accurately, the industry wants cynical, desperate writers who will write whatever cheap nasty dreck pulls in the viewers.
Paying your dues is like a gang initiation, social proof that you're willing to crawl through Albini's trench of shit to get your script into production. Every menial chore that you perform, every late night you pull, every arse that you kiss entrenches you into the industry, further investing you in the payoff of getting commissioned. The longer you've been a dogsbody, the more confident a commissioning editor can be that you won't argue when they bring in a script doctor, when they ask for a few "tweaks", when they decide that a page one rewrite is in order. They know you won't argue over the casting or ask for too much money.
Entertainment is a shit business, don't let anyone tell you otherwise.
Then maybe you shouldn't speak about it as if you do. I have heard the same advice in this article from a number of people working as tv writers (either reading articles, or as part of my mfa in creative writing), and it does seem like the vast majority of them only got where they are by "working their way up". The idea that you can just make something good enough that people can't ignore it is, in fact, the view that is hopelessly naive. It isn't like the internet where you can easily achieve massive distribution. You have to get it in the hands of a very small number of people who are swamped by an incredibly large number of people in the exact same situation as you.
The amount of good content that is generated by writers is overwhelming and, in fact, incredibly easy to ignore. Not saying you can't point to success stories of people who produced their own stuff. You can just point to more stories of people who lost a lot of money producing their own stuff and have nothing to show for it. Building relationships certainly seems to be a more reliable way to go about breaking into the industry.
I know someone who went from an assistant writing position to start in H'wood who is now co-producer of a network smash hit (Glee)... he did it by patiently building relationships and staying positive. I know "screenwriters" who sit at home all day and are supported by their wives... because they have poor social skills and feel they are entitled to money because they are smart. Don't fall into this trap, it's a dead end.
Obviously, the answer is to write terrible shit, because no one is putting any of that heaping pile of good content into consumable products.
What this means is: There are a lot of bad movies made from good scripts. Don't assume that the quality of the average finished film is representative of the quality of the average script, let alone of the skill of the average writer (who is, after all, operating under many, many constraints).
We get the same effect in our industry with games programming. Nothing about games really especially calls for endless deathmarches or 18 hour days with no overtime pay six days a week, any more than any of the many other industries in which programming is as critical or perhaps even more critical (there's more to games than programming) but somehow manages to get done in 40-ish hours a week. It's just the endless hordes of young programmers who think it's what they want to do driving the price through the floor by inflating supply until there's just no incentive for EA to treat them any better; they're not just replaceable, they're aggressively replaceable.
I really recommend against any of these careers, the risk/reward just isn't there. The risk is much higher and it turns out there are many, many other jobs out there that are just as rewarding, except without the possibility of fame for a small percentage of jobholders.
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.
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...
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.
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.
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.
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.
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).
Someone who's paid his dues by getting a PHD from CMU is more likely to get a job at Google than some guy who just read books on his own. Sure the guy who read books might create some startup, get some heat, and get bought out by google. And that can happen to a writer outside of the industry. But all things being equal, the smart money goes on the PHD.
And sure, every once in a long while you can get someone like Ross Perot, who mounts a serious Presidential campaign with ZERO political experience, but the overwhelming majority of serious presidential candidates paid their dues.
I'm sure the analogy can be applied to about any industry out there.
I just watched The Social Network, and it's a perfect example - slaving away as somebody's assistant, pumping your connections, doing something on the side, "meeting important people", you will eventually get into one of those exclusive finals clubs, and then live a life of secure mediocrity. Perhaps even at a very high level, making very good money.
If, on the other hand, you're actually obsessed about creating something great, you end up inventing facebook. There's a good chance you'll fail, too but at least you have followed your dreams and imaginations. I guess it depends on what kind of person you are, and what your goals are.
I assume that really great writers - or great anything -never did the connections thing.
The other was from Brian Chesky of AirBnB. He and his co-founders basically did whatever they had to, including selling novelty cereal boxes, to move up. He started his talk by saying how he was "powerless and obscure" and the moves he and AirBnB made, including joining Y Cominator to get to where they were profitable and "on the map" http://www.justin.tv/startupschool/b/272180383
We may not start out by fetching coffee for Paul Graham's 3nd assistant (I doubt he has one), but we do all have to start from somewhere and make whatever moves we have to in order to move up. That may involve toiling at night, moving to SF or elsewhere, or whatever. But it still just needs to get done.
Enough said, I've got some coding to do this Saturday night.
I know what you mean. I spent part of my free time this weekend teaching myself how LadderLogic works so that I will be more helpful in debugging a certain faulty machine next Monday because I'm not sure we can rely on the folks they're going to call in to give us any kind of fix.
In fact, most of his Screenwipe/Newswipe series is worth a look: http://www.youtube.com/watch?v=qpVTUdfcEMg&feature=relat...
This advice seems like the equivalent of telling someone who wants to be a game programmer to start in the QA department. You're better off just becoming a programmer. Create a game. Someone with a kick-ass demo is going to get ten times as many interviews as a guy who spends the same time pumping his connections.
Maybe I'm naive about the way television works, but if I wanted to be a writer in TV I'd start by trying to write something that was so good, people couldn't ignore me. And if I couldn't find someone to produce it, I would try to produce it myself. More than one career started with a film that only cost a few thousand dollars to produce. And if it didn't work out, at least I'd have spent the time doing something creative and productive rather than wasting my life fetching coffee and dry cleaning.