Skip to main content

NaNoWriMo 2014: Days 9-16

My NaNoWriMo attempt will not complete during the competition dates, but that doesn't mean I count it a failure. Most days I'm getting some words in, some days only a hundred or two and others a couple thousand. I keep at it, and I keep solving problems in my attempt to tell the story before me.

I won't win NaNoWriMo, but I will finish my novel. That's the thing I care about. NaNoWriMo is a great event and I hope to win one day, but right now what it represents for me is a springboard towards my dream of finishing and publishing a novel. I'm not going to let that same inspiration be a weight that drags me down, so not completing my 50,000 words before the end of this month isn't a failure. It is just the reality of finishing this novel.

The truth is, if I don't, it isn't about what I did or didn't do today. The larger factor is how rusty and out of touch I am with writing. It takes practice, like any skill, and I am woefully lacking in that practice. This novel, of course, is providing just that. And I'll continue to practice beyond the month of November. I'll practice by finishing this book no matter how long it takes. I'll practice by writing short stories that fit on a page when they strike me. I'll practice by telling stories that fall into a dozen or two pages when I need to tell them. I'll practice when revise my drafts and turn them into something better and learn from my mistakes.

I won't give up.

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

The Range of Content on Planet Python

I've gotten a number of requests lately to contribute only Python related material to the Planet Python feeds and to be honest these requests have both surprised and insulted me, but they've continued. I am pretty sure they've come from a very small number of people, but they have become consistent. This is probably because of my current habit of writing about NaNoWriMo every day and those who aren't interested not looking forward to having the rest of the month reading about my novel. Planet Python will be getting a feed of only relevant posts in the future, but I'm going to be honest: I am kind of upset about it. I don't care if anyone thinks it is unreasonable of me to be upset about it, because the truth is Planet Python means something to me. It was probably the first thing I did that I considered "being part of the community" when I submitted my meager RSS feed to be added some seven years ago. My blog and my name on the list of authors at Plan

Pythonic Defined

Introduction Losing is Good Strings Dictionaries Conclusion Introduction Veterans and novices alike of Python will hear the term "pythonic" thrown around, and even a number of the veterans don't know what it means. There are times I do not know what it means, but that doesn't mean I can define a pretty good idea of what "pythonic" really means. Now, it has been defined at times as being whatever the BDFL decides, but we'll pull that out of the picture. I want to talk about what the word means for us today, and how it applied to what we do in the real world. Languages have their strengths and their idioms (ways of doing things), and when you exploit those you embrace the heart of that language. You can often tell when a programmer writing in one language is actually more comfortable with another, because the code they right is telltale of the other language. Java developers are notorious for writing Java in every language they get their hands on. Ho