Skip to main content

Computer "Feedback" as a Writer

As a writer, I use technology to help me navigate past the gatekeepers of scriptwriting. Few people realize that when you send a script for stage or screen to any production company, the "Readers" (a job title) tend to come from MFA and Ph.D. programs. These aspiring writers earn a living determining what scripts move to the next stage of consideration (pun intended).

The "Coverage Sheet" used by film and some theater companies represents a grading rubric. If a work adheres to the formula, it has a better chance of being advanced in the process. I'm not claiming that the readers know best, but I am admitting that you need to get to the next step or your work is dead.

Based on feedback from producers, I developed Word VBA and AppleScript macros to analyze my scripts and mark potential red flags.

Some of the "rules" my macros mark are mistaken knowledge the readers insist is accurate. We know they are wrong, as writing instructors, but that does not matter to me as a scriptwriter or playwright. Readers repeatedly mark sentences like "The rose has wilted" as a passive sentence, instead of a "perfect" verb tense. My macros mark verbs to avoid, based on such feedback. The complete list of words and phrases I remove totals about 60 strings in the macro.

Other rules they enforce? The 25-word maximum sentence. The 4-line narrative block. The readers insist these "rules" represent the "right" way to compose a script. After running my macros, I know what to "fix" for the overworked readers so my script might move ahead.

Does this method improve my writing? I doubt it. But, with several productions underway, it seems to help me get the desired result. Adhering to the rules, I have plays on stage and royalty agreements signed… however mercenary that is. (Considering the topics I address, I'm fine doing what I must to get social commentary advanced.)

Reading the conversations about assessment, it's curious that as a professional writer, I find that software helps me follow stupid "rules" to earn the "grade" I want on the coverage sheets. While I am arguing to my students that we should be encourage new approaches to writing, I'm embracing the same approach to writing that they learned for the SAT or ACT essays.

Cracking the code of the rubric seems to be lifelong pursuit for some writers.

Comments

Popular posts from this blog

MarsEdit and Blogging

MarsEdit (Photo credit: Wikipedia ) Mailing posts to blogs, a practice I adopted in 2005, allows a blogger like me to store copies of draft posts within email. If Blogger , WordPress, or the blogging platform of the moment crashes or for some other reason eats my posts, at least I have the original drafts of most entries. I find having such a nicely organized archive convenient — much easier than remembering to archive posts from Blogger or WordPress to my computer. With this post, I am testing MarsEdit from Red Sweater Software based on recent reviews, including an overview on 9to5Mac . Composing posts an email offers a fast way to prepare draft blogs, but the email does not always work well if you want to include basic formatting, images, and links to online resources. Submitting to Blogger via Apple Mail often produced complex HTML with unnecessary font and paragraph formatting styles. Problems with rich text led me to convert blog entries to plaintext in Apple Mail

Learning to Program

Late last night I installed the update to Apple's OS X programming tool suite, Xcode 4. This summer, in my "free" time I intend to work my way through my old copy of Teach Yourself C and the several Objective-C books I own. While I do play with various languages and tools, from AppleScript to PHP, I've never managed to master Objective-C — which is something I want to do. As I've written several times, knowing simple coding techniques is a practical skill and one that helps learn problem solving strategies. Even my use of AppleScript and Visual Basic for Applications (VBA) on a regular basis helps remind me to tackle problems in distinct steps, with clear objectives from step to step. There are many free programming tools that students should be encouraged to try. On OS X, the first two tools I suggest to non-technical students are Automator and AppleScript. These tools allow you to automate tasks on OS X, similar to the batch files of DOS or the macros of Wor

Learning to Code: Comments Count

I like comments in computer programming source code. I've never been the programmer to claim, "My code doesn't need comments." Maybe it is because I've always worked on so many projects that I need comments  to remind me what I was thinking when I entered the source code into the text editor. Most programmers end up in a similar situation. They look at a function and wonder, "Why did I do it this way?" Tangent : I also like comments in my "human" writing projects. One of the sad consequences of moving to digital media is that we might lose all the little marginalia authors and editors leave on manuscript drafts. That thought, the desire to preserve my notes, is worthy of its own blog post — so watch for a post on writing software and notes. Here are my rules for comments: Source code files should begin with identifying comments and an update log. Functions, subroutines, and blocks of code should have at least one descriptive comment.