NaNoWriMo ’09 Journal: T-minus 13 Days

Final search for the lost manuscript and warm-up exercises.

Back in 2007, I realized that I’d lost the manuscript for a novel work-in-progress. The working copy was lost in a hard disk crash. I thought I had backups, but it turns out the backups had not been created. I detail the steps that led up to this disaster and my thoughts about it at the time here.

When I realized that the manuscript had been lost, I spent a lot of time trying to recover it. I still have all the “recovery” files. I put “recovery” in quotes because although the file had contained 97 pages of text, I only recovered about two pages. Not much of a recovery.

Gathering the Remains

Yesterday, I went through those files again, trying hard to extract some more text from them. No matter how I tried, the only thing I could get was the same two pages: about a half page from somewhere in the middle of the work followed almost immediately by the text at the very beginning. Just the fact that the text does not appear in order should tell me something. The hard disk that crashed was almost full. Chances are, the recovered “files” are not whole files but bits and pieces of other files mixed in with my manuscript text. In other words, what I recovered was all I’ll ever recover because the rest is gone forever, written over by other text.

This is the book I’ll be working on for NaNoWriMo this year.

I extracted the usable text from one of the recovery files and put it in a brand new document. Then I tracked down the other files I’d been keeping with the manuscript as I worked on it: a FileMaker Pro file that neatly recorded the details about eight of the main characters and an outline that broke down the plot into chapters with lots of notes. Although I had this outline in Scrivener as well as Microsoft Word — I likely created it in Microsoft Word and then imported it into Scrivener with the idea of writing there — I won’t be using Scrivener to write. I’ll stick to Word.

I also tracked down some index cards I’d been using to keep track of the plot and characters and make detailed notes such as maps. The book is a mystery and the murder takes place outdoors, so maps are an important part of my preparation process. I’d done quite a bit of preparation when I began the project back in 2005 (I think) and just about all of that material was still available. It’s just the manuscript itself that I lost because of my own stupidity and carelessness.

Warming Up

And this brings up the point for today’s journal entry: in the weeks leading up to NanoWriMo, participants should be preparing for the task of writing. Create your characters and build your plot now, before crunch time. Take detailed notes on index cards or in a computer-based outline, or with some other tool. Visit the world of your characters and story in your mind and take detailed notes about what you see and hear and feel.

This should be an excellent warm-up for NaNoWriMo’s writing process.

Here are a few other suggestions for those who are participating:

  • Decide now what kind of schedule you’re going to keep for NaNoWriMo. Will you write first thing in the morning, while you’re still fresh? Will you write after work? After you get the kids off to school? Before you pick them up? Or are you lucky/unlucky enough to not have anything to prevent you from writing all day? No matter what your time is like, decide now when you’ll write and be prepared to stick to it.
  • In the days leading up to NaNoWriMo’s start, spend your scheduled writing time preparing to write. Organize your workspace. Get out your notebooks or index cards or computer-based outliner. Do whatever research you need to do. Make notes about your characters and plot. Draw maps and diagrams. Spend at least 50% of the scheduled time doing this every day you plan to write.
  • Think about the things distracting you during this warm-up period. Are Twitter and Facebook and your e-mail client calling out to you? Turn off your router or WiFi card. Are you getting phone calls from friends wanting to chat? Shut off the ringer or take the phone off the hook. Is your family making too much noise or interrupting you? Close the door or explain that you need to work during this scheduled time every day. Learn about these distractions and how to handle them now, before the month begins.
  • Get your need to participate in NaNoWriMo writer’s forums (or other writer’s forums and blogs) out of your system. Some folks claim that the forums give them support and ideas. If you’re one of these people, now is the time to check in and participate. Use the other 50% of your scheduled time to do this. But get it out of your system now, before crunch time. Online forums are a procrastination tool. Every minute you spend online, is a minute you’re not writing. You know this is true. Don’t make excuses to waste time.

This is what I’ll be doing (and writing about here) in the days leading up to NaNoWriMo’s start.

Any comments? Use the comments link or form for this post to share them.

NaNoWriMo ’09 Journal: T-minus 14 Days

The start of a NaNoWriMo journal.

Yesterday, I spent a lot of time reading old blog entries as part of the process of adding excerpts that would appear in search results.

And now I must go off on a tangent to explain why….

On Tags and Excerpts

A few weeks ago, I added a feature to this blog that would list related posts at the end of each post when viewed in single page view. (If you don’t see what I’m talking about at the end of this post, click the title of this post to switch to single page view and you’ll see it.) This feature uses the tag feature of WordPress to match the current post’s tags to other posts in this blog. The posts with the most tag matches are listed as related. Makes sense to me and it actually works pretty well if all the posts are properly tagged. I set this up so it displays an excerpt after the post title. I tend to use vague titles in many of my posts — a blogging no-no, I know — so the excerpt helps readers get a better idea of what the post is about.

The trouble is, if I don’t create a custom excerpt, WordPress uses the first bunch of words — 50, I think — as the excerpt. This is not satisfactory. So I need to go through all those old posts and update them so they have excerpts. While I’m at it, I’m also updating the tags.

And, of course, I’m reading a lot of those old posts.

Why This Blog Exists

This blog has been around since October 2003 — six years this month. As I’ve explained elsewhere on this blog, I embraced the idea of blogging early on. I’d always wanted to keep a journal of the things going on in my life and blogging seemed the way to do it. Rather than rely on myself to keep a diary or journal that only I read, I could put a lot of my thoughts and experiences on the Web where others could read about them. Their comments and other means of interaction could help me understand other points of view and grow as an individual.

Sounds silly and idealistic? I don’t think so. I’ve met a lot of people through blogging — people I’ve become friends with. Miraz, for example, co-authored a book about WordPress with me a few years back after we met on my blog. Ann flew with me once and has introduced me to other people after finding me on another site I manage, wickenburg-az.com. There are other folks who have connected with me through my blog. They’ve all made my life richer and have given me good reason to continue blogging.

So, with 1,910 blog posts on this site and another 100 or so in the archives still waiting to be imported (long story), I’ve built quite a journal with plenty to look back on.

I do want to mention here that I’ve had a personal Web site since 1994. This blog is simply the current incarnation of it.

Back to My Original Train of Thought

So, as I was saying, yesterday I spent a lot of time reading old blog entries. It reminded me why I started this blog — as a journal of my life. So it makes sense to journalize my NaNoWriMo ’09 experience as it happens.

I announced that I was thinking of participating in NaNoWriMo this year in a blog post yesterday. I’d actually written the post the night before, but the Internet went down (as it often does in Wickenburg) and I wound up posting it the next day. That was a big step for me. Although I didn’t say for sure that I was going to participate, publicly suggesting that I might was enough to get me thinking very seriously about it.

And if I move forward — which I expect I will — I thought I’d journalize the process for future reference.

Just Say No to Forums

I don’t think the digital ink had dried on that blog post when I got my first query from a Twitter friend:

so whats your userid on NanoWriMo ? you can probably guess mine ;)

I could guess his, but I won’t share it here. My response was this:

I will not be participating on the NaNoWriMo Web site or forums. I don’t see any benefit.

My advice: When you’re ready to start writing, stop goofing off on the NaNoWriMo site. You can’t get work done there.

Indeed, I’d checked out the NaNoWriMo site back in 2005 when I’d first heard of NaNoWriMo. I was appalled. The site seemed to exist primarily to raise money — $110,000 — to build libraries in Laos. It was heavy on the NaNoWriMo-branded merchandise and requests for donations. Someone was obviously making money — possibly lots of it. It really irks me when I see people or organizations preying on wannabe writers.

The forums were full of NaNoWriMo participants chatting about writing or not writing. It seemed to be an extraordinary waste of time. Why would you spend any time participating in a forum when you could be spending that time actually writing?

Remember, the goal of NaNoWriMo is to write a novel-length work. I think the number of words tossed around is 50,000. With 30 days in November, that’s nearly 1,700 words a day every day for an entire month. Miss a few days and that number rises dramatically.

It seems to me that a serious author should be more focused on the writing task, not the socialization aspects of yet another writer’s forum.

Another Twitter follower had this to say about the forums:

lol maybe not but its addicting – as is twitter this year for me. :p It’s good advice though :)

I replied:

I haven’t checked it out this year. I was turned off last time I was there. Lots of people chatting, no one writing.

She replied:

Hmm… well that’s what the forums are for. You write the novel in your own time. For me the forums are a break during writing.

I’m afraid I let my cynicism get the best of me in my response to that:

If I need a break from writing, the last thing I want to do is visit a forum full of people whining about writing. IMHO.

I later pointed out the fact that I’m a cynic and linked to my first blog post about NaNoWriMo back in 2005.

What I also should have linked to is one of my more popular posts, “Why Forums Suck.” I think it pretty much covers my opinions on forums in general. Although a well-moderated forum can be an incredibly useful tool for getting and sharing information, the vast majority of forums have a signal to noise ratio that’s just too low to be worth wasting time on.

And I’ll go back to my original point: why participate in a forum if you can spend your energy writing the actual novel?

The way I see it, the NaNoWriMo forums may have value now, before the month begins. But come November 1, the serious writers should pretty much abandon it and get to work.

100 Monkeys?

I’ll step out on the line one more time here to remind folks that the goal of NaNoWriMo is to write a complete novel. That means it needs a beginning, middle, and end. It needs character development. It needs plot and subplots and underlying themes. It needs dialog and description. It needs to create loose ends and tie them all up before the last page. It needs to be compelling so someone will want to read it and written in good English (or whatever language you prefer) so someone can read it.

When you write a novel, you’re telling a story.

What I took away from my NaNoWriMo non-experience back in 2005 was that people seemed to think it was more important to get the 50,000 words out than to actually write a coherent piece of literature. Even one of my Twitter friends this year gave me this impression when he wrote:

Doubt I’ll make anywhere near the 50,000 words.. real life will get in the way ;)

It’s not the word count that matters as much as whether the entire work holds together as a novel.

100 monkeys with typewriters can churn out 50,000 words of text in a month. If you’re participating in NaNoWriMo, don’t be a monkey.

On Life Getting in the Way

The above quote brings up another topic for consideration: the responsibilities of life preventing you from completing a NaNoWriMo project.

The main reason I’ve never participated in NaNoWriMo is because of work and related responsibilities. I write for a living. The last thing I want to do at the end of a day full of writing step-by-step instructions for completing a mail merge with Word (for example) is spend any more time in front of a computer, writing.

I also travel extensively and, when I do, I have numerous responsibilities for either getting work done or seeing to the safety and comfort of passengers. Clearly, NaNoWriMo would interfere with my ability to perform while on the road.

Notice that I said that NaNoWriMo would interfere — not that my work would interfere with NaNoWriMo. That’s because if I participate in NaNoWriMo, it will become a priority in my life. That’s not to say I won’t do anything else — I do have other priorities. It just means that I won’t let life get in the way (if I can help it).

Isn’t that the point of NaNoWriMo? To force you to finish the novel in a month? To make time for it? To make it happen?

And this goes back to something I said back in 2005: You cannot write a novel without the complete support of your significant other or family. Fortunately, NaNoWriMo makes this easy. After all, you only need their support for a month.

More Coming

I think I’ve written enough about this for today, so I’ll stop here. Tomorrow, I’ll get specific about what I’m doing to prepare for NaNoWriMo.

Are you participating in NaNoWriMo? Let us know by sharing your comments — and perhaps a link to your own journal — here.

NaNoWriMo ’09

Is this the year for me?

As I finish up a crazed month and a half that included of two 6-day helicopter excursions and a week-long trip to Ventura, CA to record a new video training course for Lynda.com, I find myself with an almost empty schedule — right before the start of National Novel Writing Month (NaNoWriMo).

The idea behind NaNoWriMo is to write a novel in a month. The quality or marketabilty of the novel doesn’t seem to matter. Apparently, it’s more important to get the words out, preferably to complete a story, than to write something that might one day be published.

Whatever.

I commented extensively on NaNoWriMo back in 2005. I didn’t have much to say about it that was nice. I expanded on my thoughts in a post a few days later. You might want to read those two posts before you continue. My opinions haven’t changed.

In fact, my opinions were confirmed just today. I happened to be in a Barnes & Noble bookstore in Flagstaff, AZ. On a little table near the coffee shop area was an arrangement of books for and about NaNoWriMo. Despite the fact that November is still two weeks off, publishers and bookstores are cashing in on the needs of wannabe writers, offering them guidance for writing a novel in a month. I counted eight titles, from a small paperback to a shrinkwrapped “kit.”

I didn’t buy any of those books. I’ll never pay for anything branded as NaNoWriMo merchandise or in support of NaNoWriMo or even designed to help writers succeed in their NaNoWriMo efforts. I detest the very idea that organizations and individuals are trying to cash in on NaNoWriMo.

I’ve never participated in NaNoWriMo. My excuse is that I’ve just been too busy. When you spend all day writing about computers or something equally dull, you don’t want to spend your evenings writing.

I don’t have to prove I can write a book in a month — I’ve already done it. More than once. And my books have been published. And I’ve even made money on them.

But this year, I’m thinking I might use the ticking clock of NaNoWriMo to write the novel I started and lost. Maybe NaNoWriMo can motivate me to finish it.

So this week, I’ll pull out my notes and look them over. I’ll track down my outline and blow the digital dust off it. I’ll remember all the loose ends and how I planned to tie them up. And maybe — just maybe — I’ll be a NaNoWriMo author this year.

Anyone else out there thinking about giving it a try?

What Editors [Are Supposed to] Do

And what they’re not supposed to do.

As I travel across northern Arizona by helicopter, escorting two paying passengers among Arizona’s natural and semi-natural wonders, I find myself working remotely on a book project I started before I left and will finish when I return. I promised to keep the ball moving while away and that means reviewing edits of chapters I’ve completed.

It does not mean getting angry about editors overstepping their bounds and making manuscript changes they have no business making.

In an effort to educate writers and editors about the various editing jobs out there, I decided to put together this list of editor job types and duties. I’m hoping that my project editor and the miscellaneous editors she’s managing will read this and learn.

Rather than discuss all kinds of editors, I’ll concentrate on just two: technical editor and copy editor. These are the ones I work with directly most often — and the ones that give me the most headaches.

Technical Editor

A technical editor’s job is to ensure that a book’s content is accurate and instructions are easy to follow. Technical editors are widely used in the computer books I write, although for many of my titles, I’m responsible for my own technical accuracy. When a technical editor is put on a job, his duties include the following:

  • Reading the entire manuscript.
  • Reviewing all statements of fact to ensure they’re correct.
  • Trying all instructions to make sure they work.
  • Reviewing all screenshots to ensure that they’re correct.
  • Asking the author for clarification on something that’s not clear.
  • Informing the author of inaccuracies in text or screenshots.
  • Suggesting additional information that the author may have missed that’s within the scope of the book and may be useful to readers.

A technical editor should not — I repeat, not — do the following:

  • Make changes to information or instructions. That’s the author’s job on reviewing the technical edits. An exception would be to fix an obvious typo.
  • Add information or instructions. That’s the author’s job on reviewing the technical edits.
  • Ask the author questions about how the program works. The technical editor should know how the program works. If the author got something wrong, it’s the technical editor’s job to tell him — not to ask him if it’s right or wrong.

Under no circumstances should the technical editor make changes to the manuscript to introduce information or instructions that he has not verified. The author should never be required to perform technical editing chores on text introduced by the technical editor. It must be assumed by the author that the technical editor’s comments and suggestions are accurate and correct. Otherwise, why have a technical editor?

Copy Editor

A copy editor’s job is to review the manuscript and make sure the text is grammatically correct and conforms to the style guidelines established for the publication. The copy editor’s job is to improve the book, not change it. Specifically, his responsibilities include:

  • Reading the entire manuscript, or, for a revision, the portions that have changed since the previously published edition.
  • Identifying and fixing typos and spelling errors. If there are a lot of these, the author is simply not doing his job.
  • Identifying and fixing grammatical errors. One could argue that if there are a lot of these, the author probably shouldn’t be writing. I’ll agree with that. But every author is prone to making a few grammatical errors and should probably be forgiven. The copy editor needs to fix it.
  • Identifying and fixing style errors. I’m talking about usage like e-mail vs. email, Web site vs. website, and press the OK button vs. click OK. Style should be established in advance and adhered to by the author, so there shouldn’t be many of these problems, either.
  • Point out sentence constructions that aren’t clear. If a rewrite is necessary to clarify, the author should be allowed to do it. If it’s an easy fix like adding punctuation or a few words, the editor should be able to do it.

The copy editor should not do the following:

  • Change the author’s voice. It is the author’s book, not the copy editor’s. The only exception should be in the event that the author’s voice is so far off established standards that it needs changing. That’s a problem that needs to be resolved by the editor in charge of the project, though.
  • Change the author’s common usage to something the copy editor prefers. If the author likes to use a phase such as “If desired, you can…,” the copy editor should not change the phrase to “If you want to, you can….”
  • Create awkward sentence reconstructions to remove prepositions from the end of a sentence. While old-time grammar rules say you shouldn’t end a sentence with a preposition, it’s commonly done in casual voice writing. An author should try to avoid this, but should not be required to make his sentences sound like those in a college text book to do so.

There are good copy editors, bad copy editors, and copy editors who should not be copy editors at all. I love having a good copy editor; I love feeling that a revised sentence remains in my own voice but is improved. I love to learn from that. A bad copy editor, on the other hand, won’t find the errors he’s supposed to find. It’s embarrassing when they’re found in the printed book. A copy editor who makes changes for the sake of changes — as if to justify his own importance to the project — should not be editing. He should be either writing his own books or doing something that has nothing to do with writing. These copy editors create bad feelings for experienced authors and make their work a real chore.

What Do You Think?

What are your thoughts on this? Are you a writer with some editor stories to share? Or an editor with some author stories to share? Please share your comments on this post. I’d like to get a discussion going about this. I think I’m on track with this assessment, but maybe you have other ideas?

In the meantime, I’ve got to make a phone call. One of my editors needs to be reminded of her responsibilities and their limitations.

Word 2004 Does Not Like Mac OS X 10.5.8

It may be time to update Office.

I just started work on a new book revision. The project requires me to take relatively lengthy, style-laden Word documents, turn on the Track Changes feature, and edit like crazy. It wasn’t long before I was pulling my hair out.

You see, the other day, I updated my iMac from 10.5.7 to 10.5.8. I suspect that something in that update just didn’t sit well with Word 2004, which I was still running on that computer. After all, the iMac has an Intel dual core processor. Office 2004 was written for the old PowerPC processor that came in older Macs. Whether the problem was Mac OS X’s inability to run the old PowerPC application or Word’s inability to run on the 10.5.8 update is a mystery to me. All I know is what I experienced: text editing so slow that I could type faster than Word could display the characters.

Revisions, RevisionsAt first I thought it might be the document itself. It’s 40 pages of text that utilizes about 20 styles and fields for automatically numbering figures and illustrations. The document was originally created about 10 years ago and has been revised and saved periodically for every edition of this book. It pops from my Mac to an editor’s PC and back at least five times during each revision process. I thought it might have some internal problems. So I used the Save As command to create a new version of the document. The new file was about 5% smaller in size, but had the same symptoms as the original.

Next I sent it over my network to my new 13-inch MacBook Pro. That computer’s processor isn’t as quick as my iMac’s and it has the same amount of RAM. The software on that computer was different, though. I had a developer preview version of Snow Leopard installed and, in preparation for a Microsoft Office 2008 project I’ll be starting in the fall, I’d installed Office 2008 with both major updates. I opened the file on that machine and it worked just fine. Great editing and scrolling speed. Exactly what I needed.

So I bit the bullet and installed Office 2008 on my iMac. And the two major updates. And two smaller updates that became available on August 5. It took hours — the updates totaled over 400 MB of downloads and I’m connected to the internet on a horrible 600-800 Kbps connection that likes to drop. (I’m living in a motel right now, traveling for my helicopter business.)

The result: All the performance issues are gone. Word is snappy yet again on my iMac.

You might ask why a person who writes about Microsoft Office applications had not yet upgraded to Office 2008. This all goes back to last year’s revision on this project. I actually did upgrade but then I downgraded. It was mostly because I needed the macro feature of Word, which wasn’t available on Word 2008. I’d upgraded my iMac last year, but when I decided to reformat my hard disk to ward off computer issues I was having (which were apparently caused by a bad logic board), I reinstalled Office 2004 instead of 2008. You see, I liked the old version better.

But it’s obvious to me now that I need to keep moving forward with the rest of my technology if I want it to perform as designed. Everything must be in sync. If I want to keep using Word 2004, I should use it on a computer that has the system software available during Word 2004’s lifespan. My old 12-inch PowerBook would be a good example. It has a G4 processor and runs Tiger. That’s as advanced as it will ever get. Office 2004 is a perfect match for it.

If there’s a moral to be taken away from this story, it’s simply that if you want your hardware and system software to be new or up-to-date, there will come a time when you’ll have to update the applications that run on it. Bite the bullet and do what you have to. It’ll be worth it.