Skip to main content

NaNoWriMo 2014: Day 4

I ended today with only 6671 words. Staying on par would have been 6667 so I was only four words over, and worse I only wrote 1600 words today. That's technically under goal for the day, but I'm on pace for the month. I made the mistake of not getting even a little writing time in during the morning, before work, so I had everything to do sitting down at night. If I aim to get back on track I need to get in 30 minutes tomorrow morning and the mornings after that, giving myself a head start for the day.

Jory MacKay's How I Forgot to Write was a particularly personally hitting piece to read as my daily writing motivation. If we aren't careful we can let the skills we have wane and that is certainly something I think happened to me at some point in the last five years, and regaining those skills is a big part of what I'm doing NaNoWriMo.

The six-step program outlined is full of gems. Among the two that I hold most closely to my own writing: Find a routine and Learn to love editing. From these two the most important lines I'm carrying away today will help motivate me.
what matters is that you set a schedule and stick to it.
 and
Writing is editing.
 But, really, you should read the whole piece.

See all my posts about NaNoWriMo 2014

Comments

Anonymous said…
Hi there, good to see that your writing improves, but could you please send *just* the Python posts to the Planet Python RSS feed? Thank you!

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

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro