An Engineer’s Guide to NaNoWriMo (or how I grew from a newbie to a veteran)
This post was originally written for the NaNoWriMo blog. You can check it out here (it's been slightly modified, but the content's basically the same).
I’m an engineer. While most of my colleagues use this as an excuse to keep themselves from writing anything, I argue it’s the reason they need to be the best writers. The concepts engineers can create in their minds still need to be communicated to the world. Concepts never imagined before. Similarly, how many writers are out there with an idea nobody has ever read, just waiting to get it onto the page? As an engineer, I have a particular set of skills—some would say “quirks”—that have helped me over the last eight years of NaNoWriMo grow from just barely finishing to writing rapidly and voluminously.
Most engineers are known for their problem-solving skills, and NaNoWriMo presents an interesting problem: how do I write 50,000 words of a novel in 30 days? Like most problems, I resort...