The Mythical Man MonthComplications Ensue
Complications Ensue:
The Crafty Game, TV, and Screenwriting Blog


April 2004

May 2004

June 2004

July 2004

August 2004

September 2004

October 2004

November 2004

December 2004

January 2005

February 2005

March 2005

April 2005

May 2005

June 2005

July 2005

August 2005

September 2005

October 2005

November 2005

December 2005

January 2006

February 2006

March 2006

April 2006

May 2006

June 2006

July 2006

August 2006

September 2006

October 2006

November 2006

December 2006

January 2007

February 2007

March 2007

April 2007

May 2007

June 2007

July 2007

August 2007

September 2007

October 2007

November 2007

December 2007

January 2008

February 2008

March 2008

April 2008

May 2008

June 2008

July 2008

August 2008

September 2008

October 2008

November 2008

December 2008

January 2009

February 2009

March 2009

April 2009

May 2009

June 2009

July 2009

August 2009

September 2009

October 2009

November 2009

December 2009

January 2010

February 2010

March 2010

April 2010

May 2010

June 2010

July 2010

August 2010

September 2010

October 2010

November 2010

December 2010

January 2011

February 2011

March 2011

April 2011

May 2011

June 2011

July 2011

August 2011

September 2011

October 2011

November 2011

December 2011

January 2012

February 2012

March 2012

April 2012

May 2012

June 2012

July 2012

August 2012

September 2012

October 2012

November 2012

December 2012

January 2013

February 2013

March 2013

April 2013

May 2013

June 2013

July 2013

August 2013

September 2013

October 2013

November 2013

December 2013

January 2014

February 2014

March 2014

April 2014

May 2014

June 2014

July 2014

August 2014

September 2014

October 2014

November 2014

December 2014

January 2015

February 2015

March 2015

April 2015

May 2015

June 2015

August 2015

September 2015

October 2015

November 2015

December 2015

January 2016

February 2016

March 2016

April 2016

May 2016

June 2016

July 2016

August 2016

September 2016

October 2016

November 2016

December 2016

January 2017

February 2017

March 2017

May 2017

June 2017

July 2017

August 2017

September 2017

October 2017

November 2017

December 2017

January 2018

March 2018

April 2018

June 2018

July 2018

October 2018

November 2018

December 2018

January 2019

February 2019

November 2019

February 2020

March 2020

April 2020

May 2020

August 2020

September 2020

October 2020

December 2020

January 2021

February 2021

March 2021

May 2021


Monday, August 06, 2007

Here's a clearly written argument for hiring fewer, better PERL programmers and paying them well above average. Key point: "a good programmer can do as much as 5-10 average programmers."

I think the same is true for writers. A below-average staff writer is almost useless: you wind up redoing all their work. (And by "all their work," I mean "all their work." I can't tell you how many free lance scripts I've rewritten 100% from page 1, based on the outline that I gave them.) A good staff writer can give you exactly what you're looking for with minimal rewriting. A great staff writer helps you bring the show to another level by showing you aspects of your concept that you hadn't even thought of -- all while keeping on time and on budget.

The effect is harder to see in screenwriting. A program is fairly easily judged by management by whether it does the job without crashing or not. One can quantify some of its parameters -- how many lines of code (fewer is better), how much processing power it eats, memory usage. It's harder for a management (producers, network execs) to tell the difference between a script that works and one that doesn't.

As in programming, there's a good argument for finding the best writer and overpaying them as much as you have to in order to get and keep them. The cost will be lower than hiring more inferior writers. I'd rather have two great staff people on this show than four so-so ones.

On the other hand, writing is not programming. If you choose your writing room well, you'll get different perspectives from everyone in the room. One writer's a single woman who smokes too much, another is a middle-aged guy with kids, another is a gay guy in a long-term relationship. One can bring the funny, another has a really good reality check.

Also, I'm not sure that writers can telecommute as effectively as programmers. I've blogged in other posts about the writing room. You want the writers to be able to break story together, and to help solve story problems on the spot. And, you want your writers to physically see the set and meet the actors so they know what they're writing for.

So the article isn't dead on for show business. But still worth a few milliplatos of thought.

Aside from Brooks' Mythical Man-Month, can anyone else recommend any books or websites on programming that seem applicable to script development?

Labels: ,


Considering your familiarity with the subject, it may be a step backwards in complexity to suggest looking at Scratch at

But for people who are not programmers, the introduction to the concepts of sub-routines and branching may spark some interesting analogies to story structure.

I also think the sharing aspect of Scratch may open up some thoughts on what happens when you share a script with another person.

By Blogger Aaron Carter, at 12:41 PM  

A couple of books that might be interesting to a screenwriter are:
Software Craftsmanship: The New Imperative by Pete McBreen (ISBN 0-201-73386-2). It talks about shifting Software Development from an engineering-focused discipline to a craftsmanship discipline with apprentices, journeyman, and masters. It was the first book that came to mind when you mentioned the snippet about 1 good programming being as good as 5-10 average programmers; that sentiment is expressed in the book.

I think it would be interesting to a screenwriter as the writing industry is already a craft. I see a screenwriter as a cabinet maker or woodworker whereas software development (currently) is more like building a skyscraper (ignore scale for this analogy, I do not mean to imply any sort of judgement about difficulty or size between the two, only the techniques used).

The second book I think would be of interest is The Career Programmer: Guerilla Tactics for an Imperfect World. This book deals with how to work around the bureacracy and idiocy in the management above you to get the best product possible. Though I haven't dealt with anyone in a screenwriting sense I can definitely tell from anecdotes that the same insanity applies.

By Blogger Joe W., at 2:48 PM  

Post a Comment

Back to Complications Ensue main blog page.

This page is powered by Blogger.