I did my taxes last month. This was the first year I got to report royalty income on a 1099-MISC form, thanks to sales of Yesterday’s Demons. That was a nice problem to have.
Let’s take a look at the current status of my Project Tracker:
I’m 7% done with the second draft of Tomorrow’s Shepherd, but honestly, that number is a little high. I bumped the bar to that percentage last month after I thought the first two chapters were done, but then I spent the rest of the month going back through chapters two and three, fixing up a few more things. I’m still not done with those two.
I mentioned in my 2016 Year-End Status Update that for a while during the drafting of the book’s first draft, I experienced some writer’s doubt. I wasn’t sure what I was writing was Not Crap. Specifically, that time was while I was writing the book’s first few chapters. I’ve finally zeroed in on what the problem was. It’s a writing problem I’ve never had to deal with before.
Tomorrow’s Shepherd is the sequel to Yesterday’s Demons, so characters and plot points from Yesterday’s Demons will inevitably be mentioned. But I also want the book to stand on its own for readers who — for some odd reason — haven’t yet read Yesterday’s Demons. And since I like that book so much, I want to tell these new readers all about it. Or more accurately, I want my characters and narration to talk all about it.
But I don’t have to go into the incredible level of detail I want to. And it’s bad if I do. The problem I finally realized was this: the early chapters of Tomorrow’s Shepherd were just telling too much about Yesterday’s Demons, and it was slowing down the pace of the story. And that’s an especially big problem because Tomorow’s Shepherd starts with a fun three-chapter action scene.
To sort through the mess, I wrote on my whiteboard “TS Chapters 2 and 3 — justify your existence.” Underneath that, I wrote down every reference to Yesterday’s Demons in those two chapters. And once I did that, I performed a brutal analysis. Every reference on that board was only allowed to stay in the story if (1) it was absolutely necessary and (2) it was communicated at exactly the right time — no earlier, no later. If it failed the first test, I said to it, “See ya.” If it passed the first test but failed the second, I found a new, more appropriate place for that particular item.
This might sound like a dull exercise, but this is actually my favorite part of writing. It’s like refactoring in software engineering — all the code you need is already there, you’re just making it better via improved syntax and more accurate placement. So that’s what I’ll be doing for a while on this new book. I can’t wait for you to read it, but only once I make sure all of its elements are in the proper order.