NaNo Advice, Part 4

Apologies!  I thought that I published this on Friday, but it turns out it got saved as a draft…

We are nearing the end of the line, folks, and once again I have some advice for myself that others might appreciate as well!

Don’t stop when you hit par.

For those who aren’t writing like crazy people (also known as participating in NaNo), the NaNoWriMo website has a stat tracker that tells you if you are on pace to finish on time.  It has a daily “par” or word count that you should be at to hit 50,000 by November 30th.

I have a tendency to breathe a sigh of relief when I hit par, close my document, and do something else.  This is not a good idea!  Inspiration hits at random times, and just because I’ve hit par doesn’t mean I’m done writing for the day.  Not to mention that it’s always a good plan to get ahead if you can.  It’s impossible to know when the lazy bug will bite or life will prevent writing for a day.  Especially as we near the finish line, don’t just stop because you have enough words.

Keep writing as long as the ideas hold out and your fingers still work!

Advertisements

1 Comment (+add yours?)

  1. Tammy J Rizzo
    Nov 30, 2012 @ 12:19:54

    Reblogged this on Tammy J Rizzo and commented:
    Even though I’ve finished my first draft and validated, this is still excellent advice. If we stop when we’ve done enough for the day but are still able to do more, then we don’t have any kind of buffer built in to carry us over unproductive days without cringing at the doubled-up efforts we need to put in later. Does that make sense?

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: