Lessons from (PseuDo)NaNo

  1. 50,000 words is a lot.
  2. I can do it.
  3. It isn’t easy.
  4. 7.8 is a really big earthquake (big enough to have its own Wikipedia page).
  5. I can’t produce creative writing on three hours’ broken sleep.
  6. Strangely, I can write scene outlines and blog posts in those conditions.
  7. A supportive spouse is worth their weight in gold.
  8. Rewards are good.
  9. The right rules can help.
  10. Sometimes you’ve just got to stop bashing your head against the wall and read.

Yes or No
50,000 words is a lot. I don’t know why exactly the NaNo people picked that exact number, but I went along with it. My final word count – well, that depends. (Lesson #11: I am better at writing than maths.) I made a note at the end of each session of how much I had written, and at the end of each day I added them up and then added them to my running total.

So far, so good. But here’s where it gets weird. Adding those daily totals together in a spreadsheet produced a different total to the running total in the planning document. Thinking myself terribly clever, I cunningly checked them against the actual number of words in the text, only to discover that that was a different total again.

So, the final word count is somewhere between 51,244 and 51,445, neither of which is shown in the chart below. (Chart made with LibreOffice and technical helpdeskry from the Caped Gooseberry.)

november

Not exactly the steady progress of the professional writer, is it? Allow me to decode.
First week: all went well. Knitting-in-order-to-think is a lifesaver. That spike on day four is largely due to the fact that I was editing a scene I pulled from the first draft, rather than writing a new scene altogether. It helps.

Second week: lower totals, but hanging in there. By this time, the Caped Gooseberry’s bronchitis was in full swing, and the completely missing day mid-week may not have been totally unrelated to a certain large country’s election results coming in.

Third week: Well. You see that tiny little snibbin of a blue dash, just above the 15? That’s Monday the 14th. 61 words. In my defence, I was shelled out of my bed just after midnight by a 7.8 earthquake and didn’t manage to doze off again until after dawn (for an hour or two). Despite the ongoing aftershocks, I decided I had to get some work done. 61 words was all I managed.

In Case of Earthquake, Do Not Tweet [cartoon]You might charitably suppose that the total emptiness of the following two days was due to ongoing aftershocks, but not really. Tuesday I spent in preparation for Wednesday, when I drove the Caped Gooseberry down the recently-reopened motorway to have his wisdom teeth out. (OK, I spent part of Tuesday in preparation. The rest was spent keeping an eye on earthquake updates.)

By Thursday of week 3 I was about 7,000 words behind, and starting to panic. I managed to write a reasonable amount in between changing the ice-packs on my dearly beloved’s distorted face and bringing him soft things to eat. Mercifully, on Friday I was able to use another section of the first draft (suitably rewritten) which did a great deal for the health of the word count.

From there it was just a matter of steadily trudging on, scene after scene, one bite at a time. What happened on Monday 28th I don’t know. It was a beautiful day, I felt good about the story, it was gathering momentum – and I just couldn’t get going. I scraped through 761 words in the morning, had other commitments in the afternoon, and spent the evening in that unpleasant condition where you know you should be doing something but you’re too tired and the more you fret about it the more tired you get. (And then you go to bed and lie awake for hours.)

Rembrandt Saskia in BedOf course, I had a scheme of rewards planned out to boost the motivation: settling down with a book once I’d hit the word-count for the day (but not before); and three chocolate mint biscuits for each 10,000 word milestone. I also had three rules: make a pot of tea, commit the work to God, and think before writing. (I arranged for some plain knitting to facilitate this, resulting in approximately 4,737 stitches knit, though not all during thinking-time.)

Committing the work to God was a big one for me. I have been trying to make a habit of finishing what I start, and writing is an area where that wasn’t happening, despite my assurance that this is what God wants me to be doing. So for me, this was not just a test to see if I could do it, or a natty way of breaking the back of the second draft. It was an act of obedience. And as is so often the case with obedience, productivity results.

I am glad to find that I can be this productive, and I have every intention of carrying on with it. Not, perhaps, to the same extent (reaching 2,500 words per day involved a certain amount of robbing Peter to pay Paul) but something close. Maybe 1,800 words per day, or 2,000. The point is to be making steady progress (Exhibit A: Week 4, above).

hole-205448_640I would like to leave you with these words from Randy Pausch’s book The Last Lecture: “The brick walls are there for a reason. The brick walls are not there to keep us out. The brick walls are there to give us a chance to show how badly we want something.”

Not for All the Jewels in the Crown

I’m having trouble sleeping. (Sleep? Sleep? I couldn’t sleep tonight…)

Württembergische Königskrone-MFr-3

I could have danced all night – the cinquepace, perhaps, although the mazurka somehow seems more appropriate for midnight dashings – but I am afraid the crashing noises would keep more than myself awake.

The problem isn’t so much that I don’t sleep. The problem is more that my brain doesn’t flick the on/off switch – which is to say the un/conscious switch – until I’ve been lying in bed for an hour or two*. Which is a waste of perfectly good consciousness.

After taking the questionnaire which recommended a 12:30 a.m. bedtime, I had the brainwave of spending that hour or two reading or knitting.

For each solution, a new problem. I have yet to master either reading or knitting in the dark, and keeping the light on kept the Caped Gooseberry awake – and no-one is recommending a 12:30 a.m. bedtime for him.

not yet read

For each problem, a new solution. I used the candle-lamp of my ancestors, which provides enough light for me to read or knit by, but little enough that the Caped Gooseberry can go to sleep.

And this is where my dastardly brain pulled the ace out of its sleeve: I don’t go to sleep until an hour or two after the light is out.

It doesn’t matter how deliciously sleepy I get with the candlelight flickering on the page, how about-to-lose-consciousness I feel, once I take off my glasses and blow out the candle, my mind knuckles down to the serious business of the night: Think About All The Things!

Well played, brain. The ball is in my court, and… I got nothin’. I already refrain from drinking tea after mid-afternoon, I have a milky drink at 8:30 p.m., turn off things with screens, follow a wind-down routine…
What more can I do? Relight the candle and keep reading? Find a copy of Virgil’s Aeneid, books 7-12, aka The Most Boring Thing Ever Written? Send a flock of neural sheep trotting one by one from parietal lobe to occipital lobe?

Neuronal activity DARPA

Do you ever have problems sleeping? What do you do? Do you know of any books more boring than the second half of the Aeneid? Please share below!

*My method of estimating duration of wakefulness without looking at bright cellphone screen for time: take ‘how long it feels I’ve been awake’ and divide by two.