Wednesday, November 16, 2011

Book Update

It is now over halfway through National Novel Writing month. At this point, I should have 25,000 words written out of 50,000 by now. Unfortunately, I've only written 7,915 words for my goal, way short of where I'd hoped to be by now.

How did this happen? For me, writing is a much lengthier process then I expected. While it may seem easy to keep all of the details about your characters to paper in your head, in reality, it's very hard to be able to recall all of the minor details that make up the story. I'm sure most authors have a system in place to assist in this, but I certainly could use such a system to manage everything in my head.

In addition to being busy and unorganized, I've also found that I have difficulties focusing long enough to decide what to write and type the words on the screen. By the time I recall the necessary points of the story, I often have a distraction which prevents me from writing. Part of this is due to my desk setup at home, and partially because I'm easily distracted.

Finally, I wanted to reflect on my tool of choice so far in this project, Google Docs. The standard web version of the application works pretty well, especially in Chrome. Occasionally in Firefox I've been unable to enter text. Refreshing the page usually resolved this issue, but I've just made the switch to Chrome to edit the book chapters.

But, the Android app is a little awkward to use. It highlights the entire row you're editing, even when that row is word wrapped. For some reason, this reminds me of vim, which is not something I want out of a tool to write a book. For programming, this might work, but as a general purpose text editor, it doesn't work.

Additionally, the up and down arrows scroll the text in the window instead of moving the cursor up and down rows. This is much tougher to work around than the purely aesthetic issue with the row highlight. On a slower Android phone like the one I use, it can take a while to load ta document to edit it. Yet, when you select a document, it opens it up for viewing. If you want to actually edit your document, you have to press an 'Edit ' button to load another screen which contains the edit elements on it. Performance wise, it took about 20 seconds to load the application, about a minute to load one of my chapters in the application, then about another 15 seconds to load the document again to edit it. A slow phone and a slow network exacerbate the performance issues with the application and the architecture around it. In the end, I've typed only a small portion of the book on my phone and done the rest of the writing on a desktop through the browser to Google Docs. Its still a good way to write a novel, even if its not as easy to write on-the-go as I was hoping.


No comments:

Post a Comment