Revision Slog – Novel as Algorithm

As I slog toward the end of my third major draft of my new novel, Untimed, I felt the need for brief procrastination in the form of detailing the process. Most people seem to discount how much grind and sheer time investment is required in writing (and revising) a novel, even a vey steady workaholic like me. Let’s do a little breakdown.

Untimed is actually fairly short, currently at 83,000 words and 38 chapters. This is MUCH shorter than my first book started out. Length is a factor because you have to iterate (i.e. read through the book a LOT of times).

Think of each major draft as a loop (I am a programmer) with various sub loops.

. Generate Idea (for the most part this kind of happens or doesn’t)

. Character Design and High Level Plotting (you could spend who knows how long on this, I don’t find it that useful upfront, most of it just comes to me while doing other things)

. The First Draft:

. Initial drafting: For each chapter (1..38) loop:

. Plot the beats in the chapter. This takes an absolute minimum of 1-3 hours even if you know exactly what’s supposed to be in there. Sometimes it takes several days of banging your head and talking to others.

. Pound out a first draft. I can do 2000-2500 words of new draft in one 8 hour day. I generally make this a chapter. Occasionally I’ll be on a roll and do two.

. Reread it to catch really stupid typos, phrasing, and make sure it makes sense (1 hour)

. Subtotal. For above book that represents 50-60 workdays (NOTE: if you take days off, it’s chronologically much longer). Notes on finishing the first draft, here.

. High level pass:

. It’s impossible when writing a chapter or two a day to see the big picture in the book, so you have to do at least one faster pass through afterward.

. I can do about 10-15,000 words a day like this, which is actually fairly brutal

. Subtotal. About 7 workdays. 1-2 full reads.

. Quick read:

. If you want to judge pacing you have to read it all in a day or two like a normal book, not on the computer

. Subtotal. 1-2 days. 1 full read.

. Draft total. About 60-70 workdays. 4-5 full reads.

. Wait for feedback:

. Since you have to finish something and send it to someone, even a paid editor will take some time to read it and return feedback. This usually takes several weeks. I try and overlap it with the cleanup passes, but it’s tricky.

. Revision Drafts (I’m currently finishing the third major redraft) so I’ve done two of these so far on Untimed:

. Plan, outline, and organize changes.

. Can take from a couple days to a couple weeks. Some thoughts on this with Untimed HERE.

. I can do about 2-3 chapters a full day of revision. So for each block of 2-3 chapters loop:

. Do the actual revision. This can be fairly grueling, involving initial big surgery, a smoothing pass, then a cleanup pass

. Reread it to catch really stupid typos, phrasing, and make sure it makes sense (2 hours)

. Subtotal. Plotting 7 days, revising 15 workdays. Generates 2-3  extra reads per chapter.

. Medium Quick read:

. Checking for consistency

. Subtotal. 3-4 days. 1 full read.

. Total for each revision draft. Approximately 25 workdays. 3-4 full reads. Notes on the second draft HERE.

. Wait for feekback. You have to find out from others, often people who have never read the book before, how a draft comes across. This takes awhile. A reader who gets back to you in a week is amazing. It often takes several and some gentle (or not so gentle) prodding. Or tossing them some money. Sometimes that doesn’t even work. I had one (paid) unemployed beta reader tell me that they couldn’t start it because it interfered with their watching TV! NOTE: Said individual did not get paid.

. Line Editing:

. When the big picture is all settled out one sends it out to an editor for Line Editing. This involves more editor time than author time, but still chunks of the book come back and one must go over the edits and install them.

. My editor will request a “compression” pass before sending it to her. This is an extra pass to try and self edit it first.

. I can do about 8000 words a day like this. Approximately 10 days. 1 read. This is brutal but can be overlapped chronologically with the editor’s line editing. I.e. I can self edit a chunk and then send it out, meanwhile self editing the next chunk while the editor is working on the previous one, then also fit in the next part (processing) of returning chunks in a pipelined fashion.

. I can “process” returned line editing at about 6,000-8,000 words a day. For each chunk loop:

. Read over the track changes version of the line edit in word, approving and rejecting various edits and making cleanups

. Copy over each scene in into the real draft. Cleanup formatting.

. Do a quick read of the chunk or chapters to make sure nothing got screwed up

. Subtotal. Approximately 12 workdays, but spread across more chronological time as the edits can’t churn out this much per day. 2-3 full reads.

. Quick read:

. If you want to judge pacing you have to read it all in a day or two like a normal book, not on the computer

. Subtotal. 1-2 days. 1 full read.

. Total for line editing. approximately 24 days. 4-5 full reads.

As you can see. This adds up to a LOT of days and a lot of passes. Finishing up the third draft here, I’m already on eight months and at least 12 read throughs, and I can look forward to several more of each.

For more posts on writing, click here.

Done Again, Hopefully

My freelance editor, the awesome Renni Browne, has officially declared my novel, The Darkening Dream, done, and ready for agents!

Now bear in mind that “done” is a highly subjective term, and that as soon as anyone gives me an idea worth doing, I’ll probably do it, and that agents and editors are bound to ask for changes. Which as long as I think the ideas make the book better, is a good thing.

The new version is 5.00i, but this is my ninth full major draft. Woah.

I remember reading Sol Stein‘s awesome book on writing, where he mentioned that The Magician took 10-11 drafts (I was then on my second) and thinking: that’s crazy! I guess not. Totally coincidentally, Renni also edited that novel, published in 1971!

So it’s been a busy week, working only on The Darkening Dream (I’ll get back to my new novel shortly). In the last 10 days:

1. We finishing our big line edit

2. I rewrote the ending again.

3. I read the entire book and made minor mods.

4. Renni and Shannon (her additionally awesome co-editor/assistant) reread the beginning and the ending and did another quick line edit.

5. I went over that.

6. I got back a critique on the beginning of the book, and made some changes based on that.

7. This inspired me to write two entirely different beginnings.

8. We eventually decided the original was better, although I moved a few nice tidbits from the new stuff over.

9. I reread the whole first half of the book, and the ending again, and made some more improvements.

10. On Sunday I rested.

So now I return to the agent game (referrals very welcome), and to the agonizing internal debate about the relative merits of self publishing in the modern (and very rapidly changing) market. And back to the first draft of my new novel (about 25% done).

If any of you beta readers want a copy of the new improved 95,000 word The Darkening Dream, drop me a note.

On Writing: Yet Another Draft

The good news is that the comments from my Nov 13  draft came back Tuesday and they were very positive, and a lot less extensive than the previous three batches. So hot off an intense 8 day mega redraft, followed by one day of toddler party, followed by a full read in one day, followed by a half day of fixing the things I found in my own read… I did another 2 day mini full draft. v4.60.

I think it’s finally getting pretty close to just needing line editing (polish and smaller scale fixes). One thing about the process, however, is that a bit like a video game before you’ve had the testers pound on it, one is not entirely sure what one has. Sure, I know the book so well I can name every one of my 300 scenes in consecutive order, quote passages, or tell you to the day and version how a scene has evolved. Still, it’s hard to judge the work as a whole without a full read — and I just did one on Monday (plus two full drafting passes since then).

This is why one needs a ready supply of beta readers. Too bad it’s illegal to lock friends in a room with the book and tell them no food until they slide notes back out under the door.

FOR MY PREVIOUS POST ON WRITING, CLICK HERE

On Writing: Passes and Plots

This afternoon I finished the rough cut of my 7th major draft of my novel, The Darkening Dream. In my process, a rough cut is a draft (in this case v4.55 — yes you can tell I’m also a computer programmer) where I’ve done all the major changes I intend, but I haven’t yet gone through and reread the whole book (again, for the 40th or so time) to fix up little inconsistencies I missed and to tweak and improve the prose specifically. Part if this is that different read and edit passes have different paces, and it’s not a great idea to mix them.

In a rough cut pass one is struggling to perform large scale surgery. To cut out big sections and sew them back together. To remove characters, objects, or character the motivations, purposes, or settings of things. I like to move fairly fast during this phase because I have to keep in my head all the little loose ends that need to be tied up (I try to write them in my change plan — a kind of chapter-wise outline of changes — which I follow as I redraft). Plus, during a big rough cut the novel is also “broken”. To me this is analogous to the period when a program can’t be compiled or crashes in some heinous way. So, I don’t really want to stop too long and noodle over a sentence. I don’t like either my novels or my programs broken. It was S.O.P. during Crash Bandicoot and Jax and Daxter to build a test disk every night that testers would play the next day. If your build was broken, this couldn’t happen and other people couldn’t work. Same with the book, I like to be able to give it to a beta reader if necessary. You can’t if it’s broken.

On a read-as-a-reader pass one drops the thing on the iPad (these days) and then read it from start to finish, jotting quick notes or highlighting problems. If you stop to fix them for too long, then you loose the feel of the book as it was intended to be read. This, by the way, is why if you want to really enjoy a book, you should read at least a few pages each day. If you take a two-week hiatus (or more), you lose too much continuity.

And finally, there is polish. In this kind of pass you line edit, or change on the fly. Improving sentences, polishing phrases, fixing errors, trimming fat, whatever. It’s possible while doing this to easily trim 5-15% out of a scene without actually removing any real content. This too has its easy analogy in programming: optimization, particularly of memory or code size (no longer very relevant). In this kind of pass you just work at the low level, and so you can move slowly.

So that was passes. Now onto plots and subplots.

In my previous major draft (v4.43 — don’t ask) my editors pointed out something huge that I was subliminally aware of as a problem, but hadn’t pinpointed the exact cause. I had two major subplots going in my book. One was the main plot, and the other was the villain‘s secondary agenda. I used to have three, but that was in versions before 4.xx.

To explain this, in v4.43 and before: There were the heros and the villains. The villains had this super bad plan going, and they had multiple sub goals serving this plan. The two main villains (meaning the ones who have points of view in my story, not the boss villains) had this separate — albiet bad — agenda to get something from a vaguely good third party. The heros were both the target some of the other offscreen villains and collateral damage of the pov villains. Now this was done originally to show that the villains were so badass that even distracted they were crazy nasty. The heros had as their agenda stopping the villains and saving themselves (nothing really wrong with that), however, they were never really able to understand the actions of the villains because of the mysterious secondary objective.

By making the seemingly simple change of merging the secondary objective and with something the heros had this entire situation was changed and improved. Now, the villains want something the heros have, and although they do much the same things they did against the third party + the collateral part, they do it all to the heros (and a little to each other, because they’re evil!). By way of analogy, before the heros and villains were on adjacent train tracks lobbing bombs at each other and trying to cut each other off at the pass, now they’re on a head-on collision course firing full time at the other. This got rid of the third parties which no one cared about, and had the net effect of creating literally dozens of additional opportunities for conflict and 5 or so new big head to head confrontations — and this is in a book filled to the brim with fights. Conflict is a novelist’s bread and butter, so this is win-win.

It’s also worth saying that to improve any work. Be it video game, novel, or whatever. When you get well articulated suggestions you have to be willing to try and view their merits objectively. This is with the end of judging if the end result would be better in an absolute sense. Of course, sometimes even if it is, the bang for the buck isn’t there, or there are tradeoffs. The changing itself, however, is part of the process.
FOR MY PREVIOUS POST ON WRITING, CLICK HERE