Skip to main content

NaNoWriMo 2014: Days 2 and 3

Yesterday I did my best to make up some of the time I lost in an opening day that knocked some of my pride out. I wrote a lot slower than I had anticipated on Saturday and I didn't expect that to change, so I took advantage of a Sunday with little plans to take up my time and had three writing sessions.

I wrote around each meal, so three through the day. My son took it upon himself to join me for two of them, and he got a little distracted when he learned what text formatting was in his word processor (Google Docs) but setup upon himself a goal of three sentences a day as a minimum, and more if he more ideas. This is a good goal for an eight year old writer.

There is a line I have to walk where I'm not encouraging him enough on one side and I'm just trying to push him because I want to share writing with him on the other. He didn't want to write on Monday, but I let it slide because of the balance I need to keep on that line.

I ended yesterday above schedule, but I'm basically on par today with 5058 words on a day when 5000 would be the goal. 58 words over barely count, so keeping ahead is going to mean a chance of pace. My plan is a 30 minute writing session in the morning after my morning pages, which can hopefully help me hit 2000 words every day.

Today I sought out a piece in my reading queue on writing and I found an interview with Stephen King on writing first lines. This is good, because I don't have a first line yet.

Open a book in the middle of a dramatic or compelling situation, because right away you engage the reader's interest. This is what we call a "hook," and it's true, to a point.
 I encourage anyone with the interest to read it, and anything else King ever has to say on writing.

See all my posts about NaNoWriMo 2014

Comments

Tektonick said…
Could you please send *just* the Python posts to the Planet Python RSS feed?

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