Writer’s Block Sucks

For the first time in my life, I suffer from a serious case of writer’s block.

Prolific. That’s the word that has often been applied to me. And so it should. After all, I’ve produced more than 55 books in 12 years. In one very busy year alone, I did 10 revisions.

But things just aren’t the same these days. Writing the books that pay the bills — computer how-to books about software like Quicken, Microsoft Word, and Mac OS X — has become real work for me. The kind of work I try to avoid doing because I simply don’t want to.

Writing Blog entries has become tough, too. I think of topics while I’m driving or showering — my two best times for thinking — and when I get in front of a computer, the words just won’t come. So I waste time surfing the ‘Net (a form of procrastination) or, worse yet, watching television.

But what’s really bothering me is my complete inability to write fiction. I’m working on a number of projects. Some of them have been in progress for years and I don’t expect to ever finish them. But one of them is something I want to finish, something I want to try to have published. I’m about four chapters into it and I’m at a complete standstill.

I’m not happy about that.

I try to force myself to write, to make personal deadlines for pages or words or chapters. But when the word processing screen is before me and the insertion point is blinking away at the start of a fresh line, I just can’t make the words come.

So I write blog entries (as I’m doing now) as a kind of consolation prize. I’m writing, aren’t I? That’s better than surfing or watching television.

I feel lost and frustrated. I have a number of other book ideas that I want to work on. They’re not fiction and I’m pretty sure I can sell them. They’ll have longer shelf lives than the computer books I usually write. But I can’t seem to get started on them.

And then there’s the 10 Quick Step Guides that I promised David Lawrence. He’s all ready to publish them. He has a willing audience. But I can’t seem to write them.

Writer’s block. That’s what it is. Like insomnia: you want to sleep but you can’t. You need to sleep but you can’t. I want to write. I need to write. But I can’t.

Let’s hope I get over this soon. I don’t know how long I can handle this lack of productivity.

Not Especially a Good Day

I have a day.

Well, I shouldn’t complain. It certainly could have been worse.

Trouble began early, when I got an e-mail message from the person I thought wanted to buy the assets of my FBO at Wickenburg. He was trying to get out of the deal. He said he didn’t need me. He said my asking price was outrageous. This coming from a man who practically begged me to sell to him and didn’t even attempt to negotiate the price.

Let’s not go there.

I contacted two people at Robinson Helicopter via e-mail. The first was to try to get my local mechanic in on the September maintenance course. Fully booked, I was told. But there was no one on the waiting list for October. The second was to see if the Robinson Helipad that comes with the purchase of a new R44 would work on my property. It was designed for rooftops, I was told. It wasn’t big enough to eliminate the dust problem I had. I should consider laying down concrete.

Not what I wanted to hear.

I was so worked up over the FBO deal problems that I couldn’t think well enough to write. So instead of knocking off two chapters to my Quicken book revision, I did only one. And that was a no-brainer chapter with very few changes to the text.

That means I’ll have to work on my birthday to get the damn book done on time.

Someone kept e-mailing me all morning at the pilotcharts.com e-mail address, asking me questions about a specific product, shipping, etc. We must have exchanged a dozen messages. I warned him that if he wanted the item shipped today, he’d have to order before 2 PM. The last message from him requested a phone number. The last message from me gave him a fax number. By 2 PM, there was no fax and no order.

What a waste of my time.

My sunglasses, which I’d ordered two months ago, finally arrived. That’s a good thing. My old ones were about to fall apart.

In fact, that’s about the best thing that happened to me all day.

Mike decided to take a trip to NJ the same week I have to be up at the Grand Canyon. He fully expected me to take the dog, bird, and horses with me. The poor dog would be locked up in the trailer for 13 hours every day, six days straight. (The bird would, too, but heck, he’s used to being locked up.) For some reason, I went along with this. Until I started thinking about it. A good thing: I found a place to board the horses for only $100 for the week. A bad thing: I couldn’t find anyone to take the dog. I didn’t even try to find someone for the bird.

So I have company with me this week at Howard Mesa.

I had to drive to Howard Mesa. If you’ve been reading these blogs, you should know how spoiled I am. I usually fly up here. It’s about 1-1/2 hours by helicopter but 3 hours by car. But I couldn’t very well fit the dog, the bird, and all my gear in the helicopter. So I took Mike’s truck. Now I have three vehicles up here. (Sheesh. It’s almost embarrassing.) The good thing: Mike filled the tank with diesel. Another good thing: because I didn’t drag the horse trailer up here, I didn’t even use up a half tank of fuel. The money I saved on fuel probably paid to board the horses. Yet another good thing: if I get ambitious, I can use the truck to take my bicycle to the airport and get some exercise during lunch breaks this week.

Nah.

It was cloudy up here when I arrived. Cloudy like it might rain. Imagine that. I haven’t seen rain in Arizona in so long, I forgot what it looks like. (It was a good thing it rained in New Jersey when I was there earlier this month. Otherwise, it would have been at least three months since I’d seen rain at all.) But the moon’s out now and I think the clouds are breaking up. I don’t think it’s going to rain.

The darn bird is doing laps in his cage, climbing all over the inside. He’ll do that until I shut off the light. Sounds like a good excuse to call it a day and put this one behind me.

Writing Under Pressure

How I hit the keyboard and produce at an alarming rate.

When I got my summer job at Papillon Grand Canyon Helicopters, my editors were quite upset. Especially Megg at Osborne/McGraw-Hill. You see, every summer for the past six years, I’ve devoted about two months to writing or revising Quicken: The Official Guide for Quicken Press, which is an Osborne imprint. The book sold like crazy in its first edition (for Quicken 99) — in fact, it was the second best selling book of all time at Osborne. Although sales have fallen off a bit, it continues to sell well and remains the top-selling book about Quicken every year.

Osborne makes money producing and selling this book. I make some money, too, although not as much as I’d like. It’s a Windows book and I really don’t like writing about Windows software. After 55+ titles (I’ve lost count again), I’ve gotten cranky and picky and would rather spend time flying than sitting in front of a computer writing about accounting software.

Can you blame me?

Anyway, my schedule at Papillon requires that I live up at the Grand Canyon every other week. Up there, I live in a trailer (which is discussed extensively in another blog ). I have my laptop, an Apple PowerBook. But I don’t have any of the other equipment I need to write computer books. And frankly, I like it that way.

On my off weeks, I assured Megg, I would work on the book. I’d reviewed information about the software’s new features and told her the book would be about a 20% revision. I’d knock it off during my off weeks in the month of June.

Well, the month didn’t start very well. My uncle passed away June 4 and I felt compelled to fly back to New Jersey to visit him one last time. That killed four days that I could have been working. That equates to at least four chapters of the 18-chapter book. To make matters worse, when I returned to Wickenburg after my trip, I got about 4-1/2 hours of sleep before I had to fly up to the Grand Canyon for my week at Papillon. Although I’d managed to finish the first chapter, I later discovered that my e-mail software had failed to deliver it to Megg & Co. When I returned to my office on June 14 — halfway through the month! — Megg still didn’t have any chapters.

After handling e-mail, voicemail, and chart orders (I run a discount mail order business for aviation charts and pilot supplies — PilotCharts.com ), I finally put my nose to the grindstone (or my fingers to the keyboard) and got to work. I revised Chapters 2 and 3 on Monday and Chapters 4 and 5 on Tuesday. It’s Wednesday and, unfortunately, I have a doctor’s appointment and a haircut appointment, so I think I’ll only get one chapter done today. But if I keep up my rate of production, I should be able to get through Chapter 10 by Friday afternoon. And I’ll probably do two more on Saturday.

The revision work isn’t difficult, especially when revising material that hasn’t changed. I read over every word and make minor changes to clarify information. I’m also adding sidebars, although I’m not convinced that they’ll really add anything of value to the book. Then I make brand new screenshots. That’s where things slow down, because I have to make the software’s screens look a certain way before I take the picture. That often requires manipulating data by creating transactions — sometimes dozens of them — to show what I need to show.

I complained a bit to Mike about the work yesterday. It’s terribly tedious and very boring. He reminded me about the “paychecks” that accompany projects like this one. That shut me up.

I’ll have the book done by the end of the month as promised. I have to. There are three more titles for Peachpit Press lined up behind it.

On Radio Interviews

I start doing radio interviews again and remember why I stopped doing them in the first place.

I’m at home, sitting at a table (my old kitchen table, as a matter of fact) in our upstairs “den.” (If we had a family, we might call it a “family room.” But we don’t, so we don’t. We sometimes call it a “TV room,” because that’s where the TV lives, but I like to think that we use the room for more than just being pacified by the universal pacifier.) During the day, this room’s two 4 x 8 windows have an incredible view of the Weaver and Bradshaw mountains, but it’s dark now and I can’t see much more than the lights in a few neighbors’ homes. It’s 7:30 PM on a Friday night.

I’m waiting for the phone to ring.

I know who’s going to call. It’ll be David Lawrence, host of “Online Tonight with David Lawrence,” a radio talk show. Or it’ll be someone who works for him, just making the connection while David does other stuff in preparation for interviewing me. That’s why he’s calling, of course, I’m tonight’s guest on his show.

Oddly enough, this isn’t the first time I’ve been interviewed today. At about noon, I had to put my day on hold while I was interviewed by Alan Ashendorf and his partner (whose name I can’t remember; sorry!). I called at precisely 12 noon, chatted for about 20 minutes as a sort of dry run for the interview, and then got asked some of the same questions all over again, along with a few others. The whole thing took 45 minutes. I think I did pretty well. I only forgot what I was going to say once and, hopefully, they’ll edit that out. That’s one of the benefits of doing a taped interview. If I sound like a moron, they can fix things up to make me sound better. Of course, if I sound like a genius, they can also fix things up to make me sound worse. Whatever.

The interview by David will be live. With listener call-ins. I hate listener call-ins. Half the time, they expect you to solve some kind of obscure problem they’re having with their computer. The kind of problem that they shouldn’t be having in the first place, so you really don’t know why they’re having it, let alone how to solve it. But I like David and he supposedly “loves” me (for reasons I don’t quite understand). And I think he’ll protect me from the listener from hell. At least I hope so.

As you might have surmised, I don’t seem too enthusiastic about being interviewed. And you might be wondering why.

Peachpit Press used to line up interviews for me. Some of them were online chats which, I can safely say, are pretty much a complete waste of time. You’d check into a “chat room” at a prearranged time, then spend 50 minutes answering questions by typing them in. There would be about eight people in the audience — people who probably didn’t have much else to do with their time. Of those people, at least two worked for the organization that was holding the chat and at least one other was a fake person planted in the chat room to ask questions when no one else had anything to ask. Call me an idiot, but it wasn’t until I commented to someone about how one particular person turned up for all my chats that I was told that that person didn’t exist. And I thought I had a fan. Instead, I was wasting 50 minutes of my day typing words of wisdom for the benefit of five people.

Peachpit also lined up real interviews, though. There was one that I did in a radio station studio in the Los Angeles area years and years ago. I can’t remember why I was in LA — I certainly didn’t go just for the interview — but there I was, sitting at a table with a mike in front of me. We were live and listeners were calling in. And my headset didn’t work right so I couldn’t hear a word anyone was saying. Needless to say, I didn’t make much of an impression on that show.

There were others, too. Telephone interviews. I remember doing one while I was up at my property at Howard Mesa. Mind you, I’m on top of a mesa (a flat-topped mountain for you east coast folks), 5 miles down a dirt road from pavement that was 15 miles away from the nearest town. I did the interview on my cell phone, plugged into the car’s lighter jack with the windows rolled up. I don’t even remember what I was interviewed about or who interviewed me. For all I know, it might have been Alan Ashendorf and his partner — they seemed to remember me from another interview today.

The cell phone interview at Howard Mesa was the last straw. The problem was, Peachpit would line up these interviews weeks or months in advance. I had to arrange my schedule around these interviews. And I didn’t like that.

One of the best things about my lifestyle is its flexibility. With a day or two of planning, I can go places and do things that keep me far away from telephones and other ties to civilization. (In the old days, before dogs and horses and parrots and airports, we didn’t even need those planning days.) But things are a bit more difficult if I have to be reachable by a talk show host at a certain day or time.

So I told Peachpit I didn’t want to do any more interviews. Or chats. They tried once or twice to line something up for me, but I reminded them that I wasn’t interested. So they stopped. That was about two years ago.

Last month, I did a project for FileMaker, Inc. It was a very good project that required me to write a 15-page, illustrated document about using FileMaker Pro with Excel. The pay was excellent — heck, I wish I could get work like that all the time. But the pay included making myself available for — you guessed it — radio talk show interviews.

Earlier this week, the man in charge of lining up the interviews told me that he had two for me — both today. And because FileMaker, Inc. paid me to do them, here I am, waiting for the phone to ring.

What FileMaker, Inc. probably wouldn’t like is that this afternoon’s interview centered around my recently released Word 2003 book. That’s not what they wanted me to talk about. In fact, they sent a detailed e-mail message to both interviewers and me, outlining what they expected us to talk about. But the PR guy also made the fatal error of sending the interviewers my Word 2003 book. They didn’t care about FileMaker. Microsoft’s Office 2003 software release interested them a lot more. After all, there are millions of Word users throughout the world. What’s FileMaker Pro? I did my best. I mentioned FileMaker Pro twice in the interview. But neither interviewer picked up on it. I think Peachpit should pay the PR guy’s fee for this one.

But in reality, I know it was all a waste of time. My Word for Windows books never sold very well — they do just well enough to warrant revisions every two years when new versions come out — and I don’t expect one radio interview to change that. There’s too much competition in the Windows world and Peachpit is a very small player there.

Peachpit did send the books as requested. So the cat’s out of the bag: they know I’m doing interviews again. I wonder if they’ll try lining something up for me.

So here it is, now 8:00 PM. According to the PR guy, the show is at 8 PM mountain time. My time. And I’m wondering why the phone hasn’t rung yet.

But deep down inside, I know why. The PR guy got it wrong. The show is at 9 PM Pacific time. That means 10 PM mountain time. Which means I’ll be staying up late tonight.

I’m wrong! They called. I’m on.

— LATER —

The interview is over and it was a lot of fun. David does a great job interviewing people.

But guess what? We didn’t talk about FileMaker Pro.

Finished “Mac OS X 10.3 Panther: Visual QuickStart Guide”

Thoughts and insights on a tough revision and the computer book publishing industry.

Mac OS X 10.3 Panther: Visual QuickStart GuideMy last entry was pretty depressing. I was under a lot of stress to get the book done. Now that it’s done and the stress is gone, I’m feeling much better. The book is nothing short of a masterpiece, if I do say so myself, and I’m extremely pleased with it. We (Peachpit Press and I) got a lot of feedback from readers about previous editions. It seemed that my VQS wasn’t considered “good value for the money” because it didn’t have as many pages as other competing books. What most people didn’t consider was that VQSes are traditionally short (around 300 pages). Mine was actually long at about 400 pages. And it was considerably cheaper than the other books. But I guess if you calculated price per page, I probably fell a bit short of the competition. And I can’t deny that buying two books (a VQS and a VQP) does cost readers more money. In defense of Peachpit, the idea behind that strategy is that not all readers need all that information and we could provide affordable books tailored to two markets. But that’s not how reviewers saw the situation.

That said, we decided to combine the two books into one title. The resulting “Mac OS X 10.3 Panther: Visual QuickStart Guide” is about 670 pages long and features 20 chapters and over 2,000 screen shots. Topic range from the most basic basics (like how to point and click) to Unix commands. The price tag is an extremely competitive $29.95 US, making it a very good value. If this book doesn’t please readers, I don’t think any book will.

Writing the book was a bit of a challenge. First, there was the merging of the content from two books. What do we include? What do we exclude? Not much. The biggest casualty was the AppleScript chapter written by Ethan Wilde, which was replaced by an AppleScript basics section in the Applications chapter. (Those interested in AppleScript really ought to buy Ethan’s book!) Almost everything else that was in my Mac OS X 10.2 VQS and VQP remained in this edition.

Of course, everything has been updated for Mac OS X 10.3 Panther. That was the second challenge. Not just the update, but merging information about new features into existing chapters. Where do we discuss each new feature? Chapter 4, which is available as an excerpt from my Web site , got quite a few new pages. So did the i-Applications chapter, which was expanded to cover iCal and iSync (neither of which was available when I wrote the Mac OS X 10.2 VQS last year). The only chapter that got trimmed down a bit was the installation chapter. I cut out the info about installing Mac OS 9.2, since that information appears in the Classic Environment chapter.

There was a lot of pressure to finish the book on a timely basis. Timing is everything in the computer book publishing world and when a hot new product hits the market, publishers want their books out first. Trouble is, authors have to work with beta software, which often changes on a weekly (if not daily) basis to get the book done timely. Mac OS X 10.3’s beta software was available for about two months before the software was finally released. But the beta software changed. Any author who wrote about early versions of the beta wrote some stuff that isn’t right.

Want some examples? The first beta or two included a Print command under the Finder’s File menu. That command disappeared before I could try it out. Those first betas excluded a Favorites folder in the Sidebar. Sometime in the middle of the beta process, the Favorites folder reappeared. Then, near the end, it disappeared again. It was almost as if Apple wanted to kill favorites, thought they would get a lot of negative feedback, and then decided “to hell with the bad feedback” and killed it. (But favorites aren’t really gone, as you’ll discover when you read my book.) Icons changed, too. Internet Connect’s new icon didn’t appear until halfway through the beta process. Any screenshot of that icon taken before the beginning of October will be wrong.

So here’s the situation: publishers want the book written quickly. Once the book is written, it has to be laid out, proofed, edited, and printed. For most publishers, this is where time is lost. From the moment the author hands over the last manuscript chapter and TIFF files to the time the book appears in print, two or more months may have gone by. So do the calendar math: if the author waits until Gold Master of the software — on or around October 15 in this case — to finalize the draft manuscript, the book can’t possibly appear in stores until December 15. So what do authors do? Under pressure from publishers, they finalize before Gold Master. As a result, their books contain inaccuracies.

Peachpit and I don’t work this way. We have a remarkable arrangement. I do layout as I write, so I submit fully laid out pages as I work. My editors mark up this draft manuscript and I update pages as the software is changed and I get edits. As a result, when the software went Gold Master, we already had fully laid out pages for about 3/4 of the book. I wrote and laid out the rest the following week. This made it possible to send our completely accurate 650+ page book to the printer only three days after the software’s release date. I expect to hold a copy of the finished book in my hands by November 14 — just three weeks after the software’s release.

Any book that makes it to stores before mine can’t possibly be based on final Mac OS X 10.3 software. It’s just impossible. And that’s not an author’s fault. It’s the fault of publishers who don’t trust their authors to do layout. Peachpit trusts me and I don’t let them down.

Next on the agenda, Excel 2003 for Windows: Visual QuickStart Guide. Another revision — but this one should be a piece of cake.