- Similar posts for 'writing':
- What is a tech reader?
- Katie writes: Kids Code!
- What I learned from NaNoWriMo 2013
- Writing and Mental Health
- 2/17/15 - Young Coders: Why twelve and up?
- 12/31/14 - Looking back and looking forward: 2014
- 12/18/14 - Katie's Year of Audio Books
- 11/18/14 - Katie learns Angular.js
- 11/17/14 - Teaching Python in your PJ's
- 11/10/14 - Why not self-publish?
- 8/22/14 - My return to Pokemon
- 8/18/14 - What is a tech reader?
- 7/14/14 - Flask + git: Easiest workshop ever
- 7/8/14 - Katie writes: Kids Code!
28 October 2013
Oh, it's that wonderful time of year again, when you realize that November is just around the corner, and you have no clue what you're going to do for Nanowrimo.
For the uninitiated, Nanowrimo is a yearly event where you write a novel in 30 days. You start on November 1 with a blank file, and you end on November 30th with at least 50,000 words. That's a breakdown of 1667 words per day, or, if you want to take a break for Thanksgiving and Black Friday, 1786 words per day.
Now, Nanowrimo is awesome. I've done it twice. It's a great way to get the gunk out of your system. Originally, I had planned to finish up all of my book work by November so I could take a month and write something silly. Well, we have a problem.
I have no plot.
I try to not bring existing projects into Nanowrimo. It's technically breaking the rules, but it's also disturbing the ethos of what the month is about. So, instead, I'm doing something a bit different: Nanoblogmo.
I have a bad habit of not posting blog posts, even though I have a queue of ideas. So, it's time to take those ideas and write 1667 words a day on them and build up my backlog again. I won't be posting them here until they're done (because y'all don't need to see a bunch of half-finished blog posts), but I will be updating my progress on my Nanowrimo profile.
Or, hell, maybe I'll come up with a plot by Friday. We shall see.
Related tags: writing