Category Archives: writing

Long Weekend and a New Story

We spent the long Memorial Day weekend up in Lancaster, Pennsylvania with my sister and her family, and my mom. The kids got to spend most of the time at Dutch Wonderland, and we spent the weekend trying to keep up with them. We also took a horse and buggy ride through an Amish farm, and I had some homemade root beer, which was excellent. This is our third year in a row getting out of town on the official east coast opening of summer, and heading up to Pennsylvania, and like the last two years, it was a great success.

I managed a little bit of writing on the novel draft, but I also started a brand new science fiction story. I’m not entirely sure where it is going yet, but I will say that the main character is a somewhat overwhelmed project manager who finds himself over his head on a new assignment. And in case anyone wonders where I get my ideas: recently I have felt like a somewhat overwhelmed project manager in over his head on a new assignment.

It’s actually a nice change of pace from the novel draft, and I think I’ve been ready for a chance of pace for a little while now.

Fighting words, or musings on pantsing vs. plotting

My friend, and fellow science fiction writer, Bud Sparhawk has some fighting words for me this morning. For context, before continuing, you should go read his post. Bud and I have given several talks on online writing tools, and pantsing vs. plotting at various science fiction conventions. Today, however, Bud made it clear that he feels plotting is the superior form of writing. While I can’t deny that it might be superior for some, I can say that it doesn’t work well for me. And so let me take up each of Bud’s jabs one at a time to give a little of my perspective of this heated debate1

“Life is largely unplotted…”

Bud writes:

Jamie writes by the seat of his pants –which is akin to running with scissors IMHO– while I choose the wiser and more prudent course of carefully plotting my works.

While it is probably beside the point, I was always taught that there is a right way and a wrong way to run with scissors. Or perhaps, a safe way, and a dangerous way. On those rare instances where I run with scissors, I opt for the safe way, holding blades curled in my fist to prevent myself from stabbing anyone, especially me.

But Bud also goes on to say that he chooses the “wiser” and “more prudent” course, and that is carefully plotting out everything he writes.

It might be wiser and more prudent for Bud, but it just doesn’t work for me. When I try to plot out my stories, the result is stories that are too neatly plotted. Everything fits together too well. Coincidence rears its head more often than it should. In other words, the stories feel plotted.

Instead, I have become a big believer in Stephen King’s suggestion that life is largely unplotted. For me, planning out too much makes the stories feel artificial. I prefer a more natural approach where the plot develops from the situation the characters find themselves in and the actions that they take. This has worked well for me. The stories I write organically, without planning every step of the way, have sold faster, and in general been more successful than those that I have carefully plotted out.

Practice makes perfect

Bud goes on to talk about my prodigious output, although he exaggerates slightly. While I have been aiming for a 1,000 words/day, I average about 850. But I do write every day, and haven’t missed a day in 656 days now. In those 656 days, I’ve written 575,000 words. So Bud is right; I write a lot.

But then, my plotting friend goes on to say:

Instead, due to his hasty and impetuous headlong dash to finish something he has to throw out most of his words, edit with a chainsaw, and rewriting practically everything.  From this I draw the conclusion that writing by the seat of your pants is wasteful of time and talent. (Emphasis is mine.)

Here is where Bud and I part company. Would a music teacher say that it is a wasteful to practice your scales? Would a medical school professor tell students it is a waste of time and talent to intern? Would professional baseball player say that it is a waste of time to practice hitting in the batting cage? Would a flight instructor tell a student pilot that it is a waste of time time practice takeoffs and landing?

Then why do we think that it is a waste of time for writers to write. Bud is correct: I write a lot, and much of it gets re-written from scratch. But I don’t see it as wasteful of time; I see it as the practice I need to develop my talent. I know of no other way to become a better writer than to write. For me, the proof is in the numbers. Prior to writing every day, I sold 1 story on average every 3 years. Since my writing streak started, I’ve sold one story or article every 45 days.

Pantsing and plotting are not opposites

I find that people think pantsing means that opposite of plotting–no planning at all. For me, at least, that is not the case. I know where my story will start, and I have an idea of where it will end. Then I start writing, working my way toward that ending. The planning happens more informally, more in realtime than it might if I plotted it out. Sometimes I hit my mark, and the story ends where I imagined it would when I started. Other times, the story surprises me. The same is true for those, like Bud, who plot everything out ahead of time.

But I also need the writing experience to be a discovery for me. Plotting out things ahead of time has the same effect on me as talking about my stories: it spoils the excitement of the story.

The most important thing is to write

Bud is a more experienced writer than I am2 and can put that experience to better use than someone with less experience. But as I see it, the only way to gain experience is to write. It doesn’t really matter whether you are a plotter or pantser. What matters is that you find the process that works best for you, the one that feels right, the one that encourages you to keep at it day after day after day, through the rough patches, and through the rejections. The most important thing is to keep writing.

  1. Not really heated. Bud and I are friends and this is, of course, all in good fun.
  2. Isn’t that a great way of saying he’s much older than me?

Progress Update on the Novel Draft

It’s been a while since I’ve given an update on the progress of the current novel draft that I am working on. For a refresher, recall that I am trying to write 4 novel drafts between March 2015 and March 2016 (a first and second draft for 2 different novels).

I struggled for a while with the first draft of the first novel. I went through 7 restarts because I couldn’t make the story work the way I wanted. I came close to giving up and moving on to something else, but I really like the story, and I decided to press on. I’m glad I did. I think I figured out the trouble I was having. It fell into 2 categories:

  1. Point of view. All along, I was writing the novel as though it was a set of notes in a notebook of the main characters, who was telling the story to some unknown audience. I kept running into problems because it felt like the main character was deliberately holding back information for no good reason. It felt unnatural. It took a long time before I figured out was that I needed to tell the story from another character’s viewpoint, one who doesn’t already know the whole story. Then it took more time to figure out who this character should be. But I finally did it, and I think things will move much better now. In fact, I think the story will be a better story because of this.
  2. Framework. I have only written one other novel draft. Part of the reason I’m trying to do more is to get the practice and learn how to do it. But writing at length has been giving me trouble. Not because I can’t do it, but because I feel like I’m adding too much filler to the story that isn’t necessary. I felt like I was handling something too big. So I began to wonder if there wasn’t some way of telling the story using smaller, more management chunks. Thanks to changes in #1 above, I found a way to do this. As it now stands, I am writing the novel as a series of 5 novellas, each one flowing smoothly into the next. Each novella is essentially a stand-alone story, that allows me to work at a length that I am little more comfortable with. But in truth they are all tightly integrated, and with the exception of the first novella, you couldn’t really read a later one without having read the first one. In that sense, the novel is more like an episodic series of novellas. This, too, seems to be working better for me.

I had planned to finish up the first draft of the first novel at the end of June. I don’t think I am going to hit that mark now. More than likely, it will be closer to the end of July or early August. Of course, that throws off the rest of the schedule I had planned. On the other hand, this is intended to be a learning experience for me, and I am learning a lot about how to make longer stories work. To that end, I am very pleased.

I have no idea if this story will ultimately work; I really won’t know until I complete the second draft. But it is a story I like a lot, and I am sticking with it until it is finished.

For those wondering, I wrote about 25,000 words total in starts and restarts on the current novel draft before finally figuring out what I was doing wrong. Some folks might see those 25,000 words as wasted. I see them as invaluable practice as I attempt to learn new aspects of my craft.

Make sure you have the latest version of the Google Docs Writing Tracker

I have had some reports of DocsList errors from folks using the Google Docs Writing Tracker. This is because those functions have been deprecated. Several months ago, I updated the master branch with code that uses the newer DriveApp object model. I have been using that code for a few months with no errors. If you are seeing errors in the last few days caused by DocsList objects, I recommend you pull the latest version of the scripts. That should fix the problem. Please see the readme for additional details and instructions.

More Updates to the Google Docs Writing Tracker

I recently pushed a new branch called “project-tracking” out to the Google Docs Writing Tracker on GitHub. This branch includes code for project-tracking that I wrote about a week ago. The changes have been working fine for me over the last 10 days or so. The one thing I haven’t done yet is update the template spreadsheet. The new code requires 2 new tabs in the spreadsheet, along with some additional settings. I’ll get to that eventually.

Meanwhile, I have been trying to figure out a way to simplify what happens each night the scripts do their processing. Right now, the scripts perform a comparison between the current working document, and a previous snapshot of the document in another folder. That snapshot mechanism takes up a lot of code, and is relatively inefficient. Over the last few weeks, I’ve been thinking about an alternative, and today, I tested that alternative out with positive results.

Every Google Document keeps a revision history of the changes to that document. Here is the revision history for a story that I worked on back in February:

Revision history

It turns out, that using the advanced Google Drive API, I can access the revisions through the API. Today I performed a test, which essentially compared the current document to the last revision of the previous day. That is essentially what the snapshot method that the script current uses does. But it does without needing to maintain two files. I can get all of the information I need from the previous revision. Ultimately, that simplifies the code for the scripts. It also simplifies setup.

There is a tradeoff, however.

You can only access the advanced Google Drive API via OAUTH2 authentication. That means configuring the scripts to be able to handle that authentication. It turned out to be a pretty straight-forward one-time setup for me, but I do this kind of thing for a living. For someone who isn’t technical, it may be a little tricker.

It will likely be a while before this major architectural change is available. There are several reasons for this:

  1. My priority each day is on getting my writing in. I do this scripting only if the writing is done, and I have time.
  2. If I were doing this just for me, it would be easy. The code I wrote today checks for the last revision from “yesterday” and compares that to the current document. Simple, right? But not everyone who uses these scripts writes every day. What happens if you skip some days. Then there is no revision from “yesterday” so the script has to know to look for the previous revision regardless of date. There are a few other uses cases that need to be considered as well.
  3. Once I have the code written, I like to test it for a few weeks before pushing it out, just so that I can work out any kinks.

That said, once this feature is in place, I think it will make for an enormous improvement. Since everything, including the revisions, is contained in the one document, there will no longer be a need to manage a snapshot folder at all, and all of that code can go away.

It also opens up the possibilities for analytics on the evolution of a document over time, which would be pretty cool, too.

My Ambitious Writing Goal Over the Next 12 Months

A Tale of Two Stories

Last week, while on one of my daily walks, I suddenly hit on why I was struggling with the novella on which I’ve been working, off and on, for the last year or so. The current working title is “Strays.” I was artificially constraining the story. I was making a mistake that I used to make, thinking I knew how long a story should be before it was finished. I had it in my head that the story was a novella, and I was trying to force that… and it wasn’t working. It occurred to me, as I turned the corner from Joyce Street onto Army-Navy Drive, that the story should be a novel. The thought was light a weight off my shoulders. I knew at once that it was the right thing to do, and I felt a sense of great relief. But also, a sense of trepidation. A novel is a big commitment.

At the same time, my friend Michael Sullivan has been trying to convince me for quite a while that I need to start writing novels. If I wanted to be able to write fulltime, novels was the only real pathway that I’d have. I’d smile and nod at Michael, and say, that yes, I knew that, but that I really enjoyed writing short stories, and wasn’t ready to give that up yet.

But when I realized that the story I was working on would work better as a novel than as a novella, I thought about what Michael said. I realized that I had another novella idea sitting around dormant, one I’ve been calling “Peacefield.” I’d planned to work on it after finishing the current one. It occurred to me that I was going to have the same problem with that one as with the current one. Maybe that one could also be a novel?

Add one final thing to the mix: I’ve been reading John Feinstein’s excellent book, Where Nobody Knows Your Name: Life in the Minor Leagues of Baseball as research for the novella. I often make comparisons between writing and baseball, and the life of a writer and that of a professional baseball player. Listening to the stories of the guys who spend a decade or more in the minor leagues, and those who try to up their game in order to make the jump to the majors, I realized that Michael was right: I needed to write novels if I was going to make it to the big leagues. In my entire writing career, I have written a single draft of a novel, which is not a lot of practice. I needed to get more experience and get it sooner rather than later.

The challenge

So I decided to challenge myself. I set a goal for myself this year to try to average 1,000 words/day. In 2014, I averaged 850 words/day, so we’re really talking about adding an additional 150 words/day, which doesn’t sound like much. For me, 1,000 words/day is roughly 40 minutes of time each day.

I recall reading in Stephen King’s excellent book On Writing that he considers a season to be the perfect length of time to write a first draft of a novel. Granted, he would try to get in 2,000 words/day, which meant 180,000 words over the course of a season (3 months). But I saw some sense in that. It gives you a timeframe in which you have to focus on the task at hand. Also, I wasn’t planning on writing a Stephen King-length book. I’m looking to hit 90,000 word. It just so happens that at 1,000 words/day, 90,000 word take me 90 days–or just about 1 season.

But one novel draft does not a novelist make. I had to write dozens of short stories before I started to sell them. I don’t think I’d need to write dozens of novels before I could sell them, however. I like to think the experience I’ve gained as a writer applies broadly. But one novel draft would certainly not be enough.

However, I had this second idea for Peacefield, thematically related to Strays, but otherwise very different. I know that after finishing the draft of something long like a novella or a novel, I need some time away from before I start on the second draft. What if I wrote a first draft of Strays in the spring, and then spent the summer writing the first draft of Peacefield? That would give me three months away from the first novel to work on something different. And what happens when I finished the first draft of Peacefield? Well, I’d need some time away from that as well. So I could spend the fall working on the second draft of Strays. And when that was done, I could spend the winter working on the second draft of Peacefield. It would mean that by the end of March 2016, I would have completed 4 novel drafts, and have a lot more experience writing novels than I currently heave

So the challenge becomes: can I write four complete novel drafts in the next year? Given that I have had no trouble writing every day for the last 600+ days, I don’t see why not. The time commitment and my ability to write every day is not a factor. What is a factor is trying to learn how to write a novel. The only way to do that is to get started.

The schedule

Here is the schedule I put together for myself. I’m using my birthday as a kind of rough starting point, simply because it’s coming and it is conveniently close to the beginning of spring:

  1. Strays (1st draft): March 27, 2015 – June 27, 2015 (90,000 words)
  2. Peacefield (1st draft): June 28, 2015 – September 28, 2015 (90,000 words)
  3. Strays (2nd draft): September 29, 2015 – December 29, 2015 (90,000 words)
  4. Peacefield (2nd draft): December 30, 2015 – March 30, 2016 (90,000 words)

360,000 words is not farfetched, considering I wrote 311,000 words in 2014, and I’m trying to up my daily goal by 150 words/day. But other things sometimes get in the way. So I am also scaling back on things that shorten the amount that I write each day. I plan on attending only a single science fiction convention in the next 12 months (RavenCon, coming up next month). I plan on strictly limiting the number of guest posts that I do, and anything that takes an usual amount of time to prepare for. Professionally, the next 12 months are all about learning how to write a novel by writing 4 novel drafts.

Outcomes

Any time I sit down to write, I am putting forth my best effort. The schedule allows me to send out the second draft of Strays to beta-readers while I spend 3 months working on the second draft of Peacefield. Still, at the end of the next 12 months, I expect to have two completed second drafts, one for Strays and one for Peacefield. After some time to work in suggestions from beta-readers and produce a clean final draft of each manuscript, I think the result will be 2 novels that I can look to sell (or for which I can seek representation).

Does this mean they will sell? Absolutely not. Just like a player who hits .350 in triple-A, there is no guarantee that a call-up will follow. Luck is always a factor (a guy gets injured, a guy gets traded), as is timing. Quality is a factor as well, and just because I’ve got two final drafts does not mean they meet the standards for publication.

However, right now, the only outcome I am seeking is to build experience writing novels. That is, as I see it, the only way to learn and improve. At the end of the next 12 months, I’ll be able to say, “Hey, I’ve written a total of 5 novel drafts for 3 different novels.”

And hey, what about the novel draft that I finished in 2013 and proposed to write the second draft this year? For now, I’ve given up on it. I still think that the idea is good, and I like the characters and the setting, but I don’t believe I have yet developed the tools to make it work the way I want it to work. In other words, I need more practice. I hope to get some by attempting four novel drafts in the next 12 months.

Of course, I’ll post updates along the way, and you can follow along with day-to-day progress over at open.jamierubin.net if you are interested.

600 Days of Writing and 600 Books Read

I wasn’t going to make a big deal about hitting 600 consecutive days of writing–which I will hit later today when I get my writing in. I’d promised that my next major milestone would come on August 23, 2015–that’s when I’ll hit 763 consecutive days. On that day, I will have more consecutive days of writing than Barry Bonds has home runs.

But, as sometimes happens, an odd coincidence has forced me to mention the fact that I have hit 600 consecutive days. It just so happens, that I am also reading my 600th book since January 1, 1996. Hitting 600 consecutive days of writing at the same time that I am reading my 600th book seemed interesting enough of a coincidence to mention it here.

What is the book? Well, it will depend on which one I finish first. (I only add a book to my list once it is finished.) I am 5/8ths of the way through The Stand by Stephen King1 as part of my Stephen King Re-Read. I am reading this book mostly in the evenings before bed.

I am also reading2 Into the Wild by Jon Krakauer. I’m listening to this while on my daily walks, and while doing chores around the house. It is a toss-up as to which one I will finish first, but whichever one I do finish first will be book #600 since 1996.

So how much writing have I done in 600 days? Well, not counting today (since I haven’t written yet), I’ve written just under 540,000 words. That’s an average of about 900 words/day. That means at my next major milestone–763 consecutive days–I should be close to the 680,000 word-mark.

I just did a little math, and if I can maintain the 900 words/day pace, I’ll hit 1 million words on about August 5, 2016, which would (coincidentally) be my 1,111th consecutive day of writing.

  1. The original 1978 version, not the uncut version released in 1990.
  2. Listen to.

Thoughts on Stephen King’s story “A Death” in the New Yorker

Stories like Stephen King’s “A Death” in the March 9 issue of the New Yorker go a long way to explaining why I love short fiction. I have this sense–perhaps a false one–that while there is no such thing as the perfect novel, there is a perfect short story. It is as rare as a perfect game in baseball, but it is achievable. Of course, it is not quantifiable the way a perfect game in baseball is. To twist an oft-used expression: I can’t say exactly what makes a story perfect, but I know it when I see it.

I can probably count perfect stories I’ve read on one hand. Ray Bradbury’s “The Rocket Man”; Harlan Ellison’s “The Man Who Rowed Christopher Columbus Ashore”; and Stephen King’s “Rita Hayworth and the Shawshank Redemption” are three. After reading “A Death” I think I could add it to the list of perfect stories.

What makes a story perfect? Again, it’s hard to say. For me, the voice plays a big part of it, but not all of it. Another element is efficiency, or perhaps a better word is “compactness.” I don’t mean length. I mean the story has just the right amount of each ingredient, not a grain more or a drop less. That, plus the voice, are the two things that jumped out at me when I finished reading “A Death.”

Stephen King has often said that in his second drafts, he takes out everything that isn’t story. “A Death” is a great example of that. There is nothing I could find in it that isn’t story. Everything, every word, every image, every line of dialog contributes to the telling of the whole. It is a story that rests in a precarious balance, like a pitcher who has two outs in the 9th inning of perfect game, and full count on the batter. Take away anything from the story, and it is no longer perfect. Add anything to the story, and it is no longer perfect.

In many ways, while reading “A Death,” I kept thinking to myself that it is a Writer’s story. I enjoyed the story as a reader. But almost enjoyed more as a writer. I enjoyed in the same way a rookie ball player might look over at a seasoned veteran and see the smoothness of their swing, the fluid motion they make ranging for a ball in the field, and think, I want to be able to do that one day. Recognizing this as a writer means that you also recognize that you have the individual skills to make it happen, but not yet the experience to put them together in the right combination to achieve that level of perfection.

Beyond the entertainment value of “A Death,” beyond my awe at the seemingly effortless execution, I finished it thinking, man, I want to be able to do that one day. It’s why I keep reading. And it’s why I keep writing.

2 Years of Writing

It crept up on my, but I awoke this morning with a feeling that the date, February 27, was vaguely familiar. I couldn’t quite place at, not at first, and then around mid-morning, it hit me. It was 2 years ago today that I began my efforts to write every day. It was also 2 years ago today when I first started to use my Google Docs Writing Tracker.

2 years of writing

Prior to February 27, 2013, I’d tried on a number of occasions to start a streak where I wrote every day. I was never successful. However, in the 2 years that have now elapsed since February 27, 2013, I have written every day, except for 2; that’s 728 days out of the last 730. What’s more, I haven’t missed a day since July 21, 2013. As of today, I’ve written for 586 consecutive days.

How’d I do it? Well, I’ve talked about here and here, so I won’t rehash it all in this post. But I do want to point out once again the cumulative effect of writing a little bit every day. In the last 2 years, I have written a total of 631,960 words. I’ve averaged 865 words/day, which for me amounts to about 35 minutes per day. I’ve sold around 15 stories and articles during that time.

For me, the most important thing is practice. I’m a believer in Stephen King’s advice that to be a good writer, you need to read a lot and write a lot. Every bit of writing I do is practice. I make mistakes, and I try to learn from them, and hopefully, as with all practice, it is making me a better writer.

High Word Count Days

As a counterpoint to my earlier post on low word count days, let me take a moment to discuss high word count days. And specifically, in the context of yesterday’s writing, where I managed to blow away my previous one-day record of 5,300 words by writing nearly 7,200 words. If you are not a writer, 7,200 words might not mean much so let me put it into perspective: it’s about 30 double-spaces pages.

Most full time writers I know consider 2,000 words a full day’s work. Since I am not a full time writer, I consider 2,000 words or better a high word count day. How many of these high word count days have I had in the last 728 days? 26 of them, making them twice as rare as a low word count day. Here are all of my high word count days laid out over time:

High word count days

Put another way: I have a low word count day (less than 250 words) about once every 13 days. I have a high word count day (2,000 words or more) about once every 28 days. I think this makes sense. Given limited time, it’s easier to squeeze in less than a page, then it is to find the time to write ten pages.

I took the low word count days and high word count days and mashed them together, and here is what I got (low = red, high = blue):

Low-High Mashup

All the white space in between are days on which I wrote at least 250 words, but less than 2,000 words.

Perhaps the most interesting thing to come out of this exercise is to find that a high word count day does not necessarily follow a low word count day. This might be true if I were trying to make quota, but since my only real goal is to write every day, I don’t feel the need to “make up the difference” after a low word count day.

Yesterday’s record was an oddity all around. I had written about 3,000 words of a first draft of a story, and yesterday, the rest of the story just kind of clicked. I wrote the remain 3,000 words almost without stopping. As I have explained before, my first drafts are for me–me telling myself the story. My second drafts are complete rewrites. Now that I know the story, I can tell it to an audience, adding all kinds of nice embellishments. But it means that I rewrite the whole thing. So I started the second draft yesterday as well, and managed to get through about 4,000 words of it before calling it quits. Thus,a 7,200-word day.

Interestingly, the more I wrote, the more I wanted to write. Writing does not tire me out the way that, say, spending 8 hours writing code does. I get mentally drained from coding, but I seem to derive an endless supply of energy from writing. Whether or not the writing is good… well, I guess my beta-readers will let me know.

In any case, I suspect it will be a very long time before I have another 7,000 word day.

There was a time when I thought I would never be published…

Once upon a time, when I first started to write with the idea to sell stories, I used to have these wild daydreams of being published. I’d finish writing a terrible short story and then sit back in my chair and imagine what it would be like just to be published, to have written something good enough that an editor was willing to pay money for it, and that readers other than my friends and family would read.

My reverie was a lot of like those silly daydreams of winning the lottery. I’d come home from class one day, and find an envelope in the mailbox. Instead of a form rejection slip, the envelope would contain a Letter of Acceptance. I had no idea what such a letter would look like, but there it was. I’d dance around the room, happy as can be, floating on the thought that I’d done it! I was a published writer.

Then I’d come back to reality, face the blank page, and wonder if it really wasn’t just a pipe dream.

One day, I sold a story. I was thrilled. A contract arrived in the mail, followed by a check, and a few months later, my first published story appeared in an online magazine. It was wonderful, delightful, and very much like winning the lottery. In the back of my mind, however, I wondered if I would ever be published in one of the big genre magazines, especially Analog, which had been around since the 1930s, and in which many of my heroes had been published.

I thought that it probably wouldn’t happen. The stories published there were just too good, the competition for space too fierce. This didn’t deter me from writing, it simply provided a new form of daydream. I’d been published, and now I would close my eyes and imagine what it would be like to be published by Analog, my name of the table of contents, my byline on a story in the pages of that revered (well, by me, anyway) magazine. No, I didn’t think it would happen, but it was fun to daydream about. And I kept writing.

Then, one day, I sold a story to Analog. I couldn’t believe it. I was thrilled, but I was sure it was a one-time thing. I kept writing. Analog bought more stories and articles from me. So did other magazines. So did some original anthologies.

These days, I don’t worry much about selling stories. In most cases, when I write a short story, I’m pretty sure I will sell it, eventually. But I’ve been writing longer and longer pieces. I’ve written a novella, and a first draft of a novel. My daydreams no longer deal in short fiction. I’ll tilt my head back, close my eyes, and imagine I’ve just gotten word that I’ve sold a novel. I can almost see it. I can almost imagine how exciting that would be. An entire book that I wrote, appearing in bookstores throughout the country. How cool would that be? Just thinking about it gets me giddy.

My tendency is to think that it probably won’t happen. Writing a novel is hard. Writing good novel is really hard. The competition is fierce, and there are lots and lots of good novels being published every week. Mine would just be static within the noise. On the other hand…

I never thought I’d really sell a story. And when I did, I never thought I’d sell a story to Analog. And when I did that, I never thought I’d do it again. But of course, I did. And so I no longer worry much about the self-doubt that I face as a writer, because while the doubt is always there, lingering in the shadows, waiting for a weak moment to pounce, I’ve shown myself that, despite the doubt, I’ve managed to achieve more with my writing than I thought possible. So why not a novel? Why not bestseller? Why not a life as full time writer? Ah, one can dream.

But one can also write.

Low Word Count Days

Yesterday, I managed to write only 112 words on the story that I am currently working on. It is the lowest word count I’ve had since April 11, 2014. I thought I should mention it here since I often talk about my writing streak and my daily averages, to show that sometimes, even the best laid plan of mice and keyboards make it hard to fit in the day’s writing. Yesterday was one of those days.

112 words does not sound like much at all. Even so, I spent 20 minutes coming up with those 112 words, and they represent a complete scene in the story. I knew that yesterday was going to be a long day. I had a lot of work to focus on at the day job. In the evening, we went out to dinner with friends. So there wasn’t going to be much time to write. I squeezed in the 112 words early in the day, thinking I might have a chance to come back to add more later, but that didn’t happen.

I’m okay with that. Even though it was only a few short paragraphs, I felt good about what I’d written, and I was relieved that I’d gotten it done early in the day, rather than stress it about not having it done yet through the latter part of the day. For me, the goal is to write every day. It doesn’t matter how much or how little.

But it did make me curious about how often I have these particularly low word counts. Since one full manuscript page is about 250 words, give or take, I’ll use 250 words as a threshold, and ask: how often have I written less than a page a day?

In the last 724 days, I have written less than a page 57 times. That’s about 7.8% of the time, or about 1 out of every 13 days. Looking at it as a timeline, my low word count days look as follows:

Low word count days

I’ve learned not to be discouraged about low word count days. Some writing is better than no writing, even if it’s a page or less on a given day.

But mostly, I wanted to show that despite my growing consecutive day writing streak, not every day is an 800 or 1,000-word day. There are plenty of days (57 day of them!) when I can barely get a page.