Death of a Manuscript

Dealing with the loss of my own unpublished words.

Last week, I discovered that a file containing the manuscript for a novel I was working on was gone.

The file lived in my laptop, which is what I was using to write it. It was backed up on my main computer’s hard disk. I had decided two or three months ago to keep working copies of all my fiction on my iDisk space. (iDisk is part of the .Mac services available for Macintosh users. It gives you 1 GB of storage space on an Apple server that can be shared among all of your computers.) The idea was that by keeping the files there, I could work on them from any computer and always have the most recent version.

Somewhere along the line, while copying the folder containing this file to my iDisk space, the file was lost. I’m not sure how it happened, but I do recall getting an error message when I made the copy. I should have investigated more closely, but I didn’t. The file was gone and because I didn’t work on it for months, I didn’t realize it was gone.

The backup copy, of course, was lost in my February hard disk crash.

I spent most of a day playing with file recovery software to get the file back. I managed to retrieve about 2 of the 97 pages I’d written.

Obviously, I’m not very happy about this. I’d been working on this project on and off for about four years. There was a lot of me in it. I’d written a lot of good dialog and some pretty strong scenes. It wasn’t perfect — the characterization on a few of the characters was just not good enough — but what was good was very good. A lot of “keeper” stuff in there.

And now its gone.

I find the task of recreating this work daunting. Lately, I just don’t feel that I have the writing skills I need to write fiction. I have my outline, my index cards for scenes, my character notes. I can clearly remember lots of the scenes and even some of the dialog. But I don’t feel confident that I can rewrite what I lost. I know that when it comes time to sit down and type it all back into my word processor, there will be something lacking. It just won’t be as good or as complete.

Fortunately, this was the only manuscript I lost (other than the partially completed Chapter 6 of my Excel for Windows book, which was easy, if not tedious, to recreate). My other fiction manuscripts remain safe, now backed up to three places. But although I’ve been toying with them for far longer — one of them originates back in my teenage years when I wrote longhand in spiral bound, college ruled notebooks — the loss of this one seems to hurt more. It was a more mature work, a more marketable work. It, unlike my other fiction scribbling, had a future, possibly in print.

Time is now my main obstacle to picking up this work and recreating it. I’m juggling two jobs: as a technical writer and a helicopter pilot. I’m having a hard enough time getting both of those jobs done. At the end of a working day, I’m mentally exhausted and not prepared to tackle a recreational writing assignment. (That’s one of the reasons I do 90% of my blogging first thing in the morning.) So who knows when this work might be resurrected?

Perhaps it’s something to look forward to in my retirement years.

Using Google AdSense Channels

Article now available on Informit.com.

My latest Informit.com article, “Using Google AdSense Channels” is now online.

From the article’s intro (written by editors, not me):

Google’s AdSense program is a very popular advertising option for blogs and web sites because it’s easy to use and can generate revenue with minimal effort. Maria Langer explains how to use the Channels features in AdSense to track which of your ads are earning the most revenue.

This article should be of special interest to bloggers and traditional Web site webmasters who try to raise revenue using the Google AdSense products.

There are two other Informit articles in the pipeline. Keep checking in; I’ll let you know when they’re released. Or check my Informit.com books and articles page for yourself to see what’s new.

Blogger's Block

Sometimes there just isn’t anything you feel like blogging about.

Those of you who follow this blog or its individual categories may have noticed a dip in new entries earlier this week. I normally try to get at least one new entry out per day. But early this week, that was difficult to do. In fact, I went three consecutive days without posting anything at all.

Why? I think I was suffering from blogger’s block.

Is there such a thing? Well, apparently there is. I just Googled the phrase and got a list of blog entries that reference it. More on that in a moment.

First, I want to talk about why it’s important to blog regularly. Simply said, your regular readers expect it. When they visit your site each day (or every two or three days, perhaps), they expect to see new content. Disappoint a visitor a few times and he might not come back. If your goal is to attract and keep visitors, it’s vital that you give them something new and interesting to read each time they visit.

The problem with that — other than the problem of being interesting in the first place — is coming up with fresh topics that you want to write about. And that’s where I was earlier this week. Bummed out by my sick computer, not happy about surfing the Web for ideas on my little laptop, busy completing my office move, occupied with Web server modifications and setting up new gigs for Flying M Air. Without input from the Web or time to think of topics, I was short on inspiration and unable (or perhaps unwilling?) to write anything new.

This is something I need to cope with. Fortunately, Darren at ProBlogger has written a series of articles on the subject of blogger’s block that has lots ideas for defeating it: “Battling Bloggers Block.” As usual, Darren has a bunch of really good tips. I recommend checking them out if you find yourself short on ideas for your blog.

Telephone Support for the Price of a Book?

Not likely.

I was driving down to the Phoenix area yesterday — my first time driving down there in months. It was a beautiful day, sunny with temperatures in the 70s. I was driving my little Honda with the top down and my iPod, connected to the stereo, blasting some classic rock. I had a 30-mile drive ahead of me on Route 60 (Grand Avenue) to get to the nearest PetSmart (or is it PetCo?), where I planned to buy some tropical fish for my aquarium. Route 60 isn’t the most pleasant road to drive on, but it’s nothing to complain about in the stretch I was driving.

I was having a good time.

My cell phone rang. The only reason I heard it is because it’s on vibrate mode and my ears were not necessary. I hit the mute button on the stereo and answered the phone.

The woman on the other end was difficult to hear at 65 mph in a convertible, so I pulled over. After all, she could be a customer for Flying M Air and I needed to hear what she wanted and to give her my full attention.

The words started coming through: QuickBooks. Book. Non-profit. How do I print checks?

It took all my patience not to explode. Apparently, this woman thought that since I’d written a book about Quicken for Windows and another book about QuickBooks for Macintosh, I could help her figure out how to print checks from the non-profit version of QuickBooks for Windows, which I had never even used, let alone written about. I don’t know where she got my phone number — it’s no longer on this site because of calls like hers — and I don’t know where she got the idea that the author of a book about a software product would be her free, technical support hotline.

I set her straight, hung up, and got back on the road. I was fuming for a short while, but the music and wind and great weather soon soothed me.

Here’s what people don’t seem to understand:

  • A book’s content is determined, in part, by the book’s project editor and page count. So an author cannot include coverage of every single nuance of a software program. The least used features are left out to make sure there’s room for the most used features.
  • An author cannot write a book about a topic unless the publisher feels that there’s enough of a market for the book to sell. That’s probably why this person could not find a book covering the not-for-profit version of QuickBooks for Windows. It’s also why I did not update my QuickBooks for Macintosh book to cover QuickBooks 2007 or my Quicken for Macintosh book for any version after 2003 (I think).
  • An author receives, on average, less than $1 per book sold. I don’t know where anyone can get one-on-one, completely personalized technical support by telephone for $1. (Even the folks in India use a script.) My point: buying one of my books does not entitle the reader to interrupt my day by telephone to ask questions about the book’s content or topics not covered in the book at all.
  • An author certainly cannot be expected to provide support for another author’s book. True story: I once got a question in my old FAQ system from someone who told me he’d bought a book by [insert author name here] and was having trouble understanding it. Could I help him? He wasn’t joking. Neither was I when I told him to contact the author of that book, not me.

This might seem like a hard line to take, but I don’t think so. I do a lot to support my work and provide content above and beyond what’s between a book’s covers. The Book Support categories you see listed near the top of the navigation bar are just an example — each one provides additional articles somehow related to a specific book. My Q & A system is also set up to receive questions that I can answer in a place where all readers can benefit from them.

That should be enough.

Link Bait?

Unintentional, perhaps, but very effective.

I’m getting ready to upgrade my blog-based Web sites to WordPress 2.1 from WordPress 2.0.4. It’s a big task for some sites and the biggest hurdle I have to jump is the plugin compatibility hurdle. This site and wickenburg-az.com rely on plugins for many of their features. If a plugin were to unexpectedly stop working, the sites could be brought down by PHP errors. This is not something I want to deal with, so I started thinking about the plugin situation. And, as I often do when I’m thinking of something that might benefit other people, I wrote an article about it and published it here.

Does that make the article “linkbait”? I suppose it does. But I’m willing to accept that label if it’s used in the context of “simply compelling content.”

It took me about an hour to write the article. (Those of you who know me and my work know that I can produce original material at often alarming rates.) It was all fresh, out-of-my-brain stuff, inspired by the WordPress upgrade instructions and compatible plugins list, which I linked to in the article. It was better organized that a lot of the posts here — especially the long, rambling ones about flying and the things that go on in my life — and it included headings and lists to make it easier to read.

It hit the site at 7:24 AM MST. Within two hours, it had been linked to by Weblog Tools Collection (thanks!) and the article with the link just happened to appear in the Dashboard for all WordPress users. That’s when all hell broke loose. Visitors swarmed over. The article collected 10 comments and pingbacks in a matter of hours. The pingbacks, in several languages, brought even more visitors. At one point, I had 29 visitors (including bots) online and 19 of them were reading that one article.

Now that might not seem like a big deal to many of you, but it’s a huge deal here. My daily visitor count, which averages about 250 per day, jumped to almost 900. And my page hit count soared to over 1250 from a daily average of 400-500. Whew! And the trend is carrying over to today; at 8 AM, I’ve already reached my daily average counts.

What’s So Special about This Article?

So the question remains: why has this one article been such a boon to the site?

In looking at the article and how it differs from other site content, I’ve come up with the following:

  • The article was 95% original. I based it on my own experience and knowledge rather than material I’d found elsewhere. This was new content — not something I read and regurgitated here. And given the 1/9/90 rule discussed earlier today, only 1% of what’s in blogs is original content.
  • The article was timely. WordPress 2.1 had been out for less than 3 days when I wrote it. (Oddly enough, two commenters said they wished I’d written the article sooner. Sadly, I have neither the time nor the inclination to work with software under development these days, especially when that software is based on a computer language I hardly know.)
  • The article provided valuable information. Anyone who jumps blindly into a major WordPress upgrade deserves all the grief he gets. To me (and apparently others), the plugin issue is serious business. My article explained why it was serious and listed things that should be done for a less troublesome upgrade.
  • The article was well organized and well written. Sure, it’s easy for me to say — I wrote it. But I can look at all of my work objectively and I can say without a doubt that among my blog posts, this article was one of my better efforts. In fact, if this post wasn’t so time-sensitive, I would have submitted it to Informit.com, which pays me to write for them. (If I had, however, it would not have reached the Web for at least a month. So yes, I gave up a few hundred bucks, but WordPress users need this information now and I didn’t want them to wait.)
  • The article was well presented. I’m talking here about readability, which I discussed in another blog post earlier this month. This post included headings and lists, which help break text into bite sized pieces and make it more scannable.

It’s gratifying that the article was found by a “WordPress authority” who found it worthy to link to. I wouldn’t be writing this post if I didn’t get the support of the folks who linked to it. They brought visitors to the article, pumping up my daily numbers accordingly.

Is it Linkbait?

Does that make the article “linkbait“? I suppose it does. But I’m willing to accept that label if it’s used in the context of “simply compelling content.” After all, I didn’t write it with the goal of getting lots of links and readers. I wrote it because it was on my mind, is a topic my readers claim they’re interested in (33% of those who took the poll said they’re interested in blogging), and is related to a topic I co-authored a book about. The article was forming in my brain — why would I keep it there if others might find it useful?

That said, I’m not one bit sorry that it has attracted all the attention it has. It’s given me a lot to think about — and more to write about here.