Production Pipeline for Fiction
September 13, 2017
I’ve been spending all my creative time proofing Errant Gods for what feels like the last eon or so. Because I am using Microsoft Word, in its infinite glory, I am now borderline psychotic. This has led me to think about other things in other, special ways…and I’ve come up with the perfect production pipeline for writing fiction. Here it is:
- Come up with an Idea.
- Think about the Idea
- Reject the Idea because it sucks
- Think about the Idea more (because you don’t have a choice)
- Decide the Idea is okay after all
- Begin writing
- Write a little more
- Decide everything you’ve written sucks
- Write more anyway
- Decide the newly written material sucks, but maybe the first batch was okay
- Rinse and repeat 9 and 10 until the novel is “finished” (which just means the real work is about to begin)
- Reread the novel, decide it sucks
- Rewrite the novel to see if anything can be salvaged
- Decide everything you’ve rewritten sucks
- Rewrite again
- Repeat 14 and 15 until either: 1) you can’t make it any better, or 2) you become so cross-eyed you can no longer read English.
- Decide it sucks, but that an editor might be able to help
- Do a quick, cursory proofread so that you don’t look like in edaot to teh aditor.
- Send it away with a smile
- Realize the novel sucks
- Get the editor’s changes back and go through them all, making appropriate changes
- Begin final proofing, using either Microsoft Word, or a spiked hammer, whichever hurts more (MS Word, trust me).
- Decide it sucks, but continue proofing
- Publish it (even though it sucks).
At one time, I thought this idea that everything you do must suck was only part of the production pipeline for new authors. Then I read an article about Stephen King where he talked about being really nervous about publishing Mr. Mercedes because he “was supposed to be that scary guy” and he was afraid his fans wouldn’t like it…
Wow. This post sucks.