Tag Archives: books

Not Enough Hours in a Day

Posted on by
1

Still too busy to blog regularly.

I’ve been neglecting this blog lately, which is something I’m not happy about. You see, I need to blog. I need to keep this journal of my life and share tips and how-tos with strangers all over the world.

So when I neglect it, as I have been for the past week or so, I feel bad about it.

I Take Work When I Need To

But the reason I’ve been neglecting things is because I’ve been so busy doing the kind of work that pays the bills. (No, blogging doesn’t do that.) As any business owner or freelancer can tell you, there isn’t always paying work to do. Sometimes, after a dry spell, you have to take the work that comes along.

And that’s how it is with Flying M Air. Summer in Wickenburg simply sucks. I can’t put it any other way. There are few people around and none of them want to fly — including me. It’s just too damn hot. So with just one gig in all of July and just three or four in all of August, I was personally funding Flying M Air again, paying its bills through the dead summer months.

And Flying M Air doesn’t have small bills to pay.

When September rolled along, I was anxious to do rides at the Mohave County Fair for the third year in a row. And right after that, were two good gigs with photographers over some of Arizona’s most scenic areas. Although the Fair gig was a bust this year, the two gigs that followed it earned me more than 15 hours of revenue time. That’s enough to keep Flying M Air in the black for four to five months. Best of all, I have another very lucrative gig lined up for Lake Powell, Monument Valley, and Shiprock at the end of September and beginning of October.

I Work Two Jobs

All these gigs have been keeping me from my office for days at a time. That means I can’t do the work I need to do for my other job, the one that funded Flying M Air in the first place.

I’ve been working on my 70th book, a revision of my Mac OS X Visual QuickStart Guide for Leopard, since July. It’s a 750-page volume and I decided this year to tear it apart, reorganize it, and rebuild it from the ground up. I’m nearly done, but it’s been a long, hard task from the start.

It’s always hard writing a book about software when all you have is beta. Betas aren’t always stable, so they occasionally crash at the most inopportune times. Betas aren’t always final, so the thing you wrote about two weeks ago might be different today. It’s a constant process of review and revision.

It’s also a process of learning how new features work. Sure, there’s some onscreen help for some of the new features. But it’s spotty and incomplete, designed to teach basics. It’s best used as a starting point for learning more. Only by “playing” with the feature and experimenting with it can you learn the little tricks that give the book value to readers. That’s my job, and it’s both fun and frustrating sometimes.

Tight Scheduling

As I write this, aviation photographer Jon Davison is in my kitchen, cutting up a cantaloupe for his breakfast. Here’s here to photograph and write about Flying M Air and my helicopter for a book he’s writing about Robinson helicopters. We’ll be flying today and tomorrow and probably on Tuesday. Today’s the air-to-air portion of our photo work; we leave in 45 minutes to fly in formation with my buddy Dave, who owns a Hughes 500.

Although this isn’t a paying gig, it’s important. Jon’s coverage of Flying M Air will help me promote the company. The book, when released, will show readers the kind of work I do and places I go. I’m eager to promote my 6-day excursions and this will definitely help.

So I’m squeezing Jon into my schedule. A few days with him followed by a few days of Leopard followed by a few days in the Four Corners area, flying photographers around.

October is another busy month, with gigs on three of the four weekends.

What To Look Forward To Here

When the Leopard book is done, I’ll begin writing short how-to pieces for this blog about it. But don’t expect to see them before Leopard is released. I take non-disclosure agreements very seriously and don’t have any desire to get Apple, Inc. pissed off at me.

And if you like reading about flying, keep checking in. I’m sure I’ll have some things to say about my work with Jon — hopefully, with photos — and the photographers I’m working with at month-end.

Working Hard

Posted on by
2

Writing, flying, writing, flying, repeat, repeat, repeat.

I realize that I haven’t been blogging lately. I have a good excuse. I’m unbelievably busy with work.

I have a drop-dead deadline for my Leopard book coming up very quickly now. So whenever I’m at home, I’m in my office with my fat butt planted in the chair in front of my computer, writing about Leopard. The book is coming along very well, but not without some minor problems. Still, if I keep at it, I’ll get it done on time.

Trouble is, I’m not spending much time in my office. After a seriously crappy-to-the-point-of-wasted-time gig in Kingman last weekend, I had to fly up to Page to take some photographers around Lake Powell. For three days in a row.

Confluence of San Juan and Colorado RiversI love Lake Powell. I think it’s one of the most beautiful places on earth. And if you think it looks great from the ground or water, you should see it from the air! But after a 4 hour flight on 4 hours of sleep today, I decided I’d had enough of the Lake. Fortunately, I’m going home tomorrow, after dropping off one of my clients in Phoenix.

I’ve been in the Marriott Courtyard here since Monday night. I’ve had five flights totaling over 10 hours of billable time, with about 3 hours more to come. Great for the Flying M Air bank account, which can always use a good cash inflow — especially after a slow summer in Wickenburg. But not great for the Leopard deadline.

So now I’m sitting here at the desk in my hotel room with two laptops in front of me — my MacBook Pro test mule running the latest Leopard beta and my trusty 12″ PowerBook G4 — revising text and making new screenshots for my Leopard book. I’ll finish Chapter 7 today and, with luck, start Chapter 9. (No, I’m not doing them in order.)

Tomorrow, I’ll check out of here at 7 AM and take my luggage — including my “portable office” — to the airport. By 8 AM, I hope to have my passenger on board for the flight to Phoenix. With cooperative weather (read that, “no headwinds”), I’ll be at my desk again by 1 PM, laying out the chapters I wrote in Page. Friday, I’ll be in my office all day.

Then, on Saturday, I pick up another photographer. He’s from Australia and he’s doing a coffee table book about Robinson helicopters. I’m one of his featured operators. I’ll fly him around for a few days, taking time to work on the Leopard book in early morning hours, before he’s awake. He leaves on Tuesday. Then I have two more days in my office before another helicopter gig at Lake Powell, Monument Valley, and Shiprock.

Anyone who thinks being a freelancer or owning a business is an easy living should walk in my shoes this month. It’s times like these that I think back with a bit of longing for those cubicle days, when I spent more time shooting the bull with co-workers than working long hours to meet deadlines and client needs.

But by mid-October, things should be back to normal. Until then, bear with me. On the priority scale, blogging has slipped behind a few more important tasks.

On Revisions

Posted on by
Comment

At the halfway point of my Mac OS X book revision.

Yesterday, as I completed the revisions to Chapter 10, I reached the halfway point in my revision for Mac OS X 10.5 Leopard: Visual QuickStart Guide.

No, the book isn’t 20 chapters long. It’s 27 plus an appendix. I’ve revised 14 chapters. I’m not revising in order. I’m revising in the order I think it might be safe to revise in. Some features are still in flux and if I revise based on what I see, I’ll likely have to revise again.

And no, I can’t tell you what I think might be in flux. I’m under non-disclosure and I take that stuff pretty seriously. That’s also why you won’t find Leopard screenshots here (yet). And why I haven’t written any articles about the new features (yet).

This is a Deep Revision

I’ve settled into a pace of about one revised chapter per day. That might seem like a lot. It is, especially since I’m doing what I call a deep revision.

I not only write my Visual QuickStart Guides, but I also do layout for them. This is called packaging — the author provides final files to the publisher, who then (after editing, of course) sends them on to the printer.

I currently use InDesign CS3 for all my layout needs. But that’s not what I was using when I wrote the first edition of this book, which covered Mac OS 8, back in 1997. (I still remember that book’s release at Macworld Expo in Boston. Peachpit sold out on the first day of the show, but UPS was on strike and we couldn’t get any more books in.) In 1997, I was using PageMaker. And that’s what I used to create the original book files.

A revision is a revision. That means you start with something and modify it to bring it up to date. So each year, I’d start with the previous year’s file and modify text, replace screenshots, and make various other changes to bring the content and file up to date.

Every time I switched to a new version of my layout software — PageMaker became InDesign 2 which became InDesign CS which became InDesign CS3 — I can’t justify the expense of updating my software for every release — I’d simply convert the file to the new version at the beginning of the revision process.

Over the years, this led to inconsistently set up files. Sure, the differences were minor, but they were there. And it bugged me that there were tiny differences in the style definitions and that some text included indexing codes from a failed experiment with the indexing feature and that the Zapf Dingbats font applied to bullets wasn’t working right in all files. And that in some chapters, each page was a different InDesign “story” and in others, the stories would go on for several pages.

So this year I decided to clean up the files by recreating them all. I built a brand new template in InDesign CS3, adding the staggered tabs that many other VQS books include but mine never had. I took full advantage of InDesign’s nested style feature to automate bullet and reference formatting. I made my styles intelligent and highly functional.

Then I got an InDesign plugin that enabled me to export the individual stories in a single chapter file as one big story in plain old text. I do this for each chapter. I make sure the text has smart quotes and paste it into my template. I then manually reapply all the styles as I go through the text and edit it to bring it up to date.

Along the way, I reorganized much of the content to remove 2 chapters, add 5 chapters, and move a bunch of content around.

A deep revision.

Other Revisions

Contrast this with the last book revision I did. That was for another publisher which doesn’t allow author packaging. Instead, the book is submitted as a series of Microsoft Word files.

I start with the previous year’s “final” files. I turn on the revision feature so all my changes are marked — supposedly for the benefit of the copy editor, so she doesn’t re-edit the whole thing — and go at it. The result is a mess that only gets messier as the book goes through the editing process. In the end, it’s all cleaned up, laid out and sent to me as proofs so I can make any final corrections to it.

If the software I’m revising the book for hasn’t changed much, this can be incredibly quick — I can sometimes turn out 3-4 chapters in a day, with plenty of time for my morning coffee, blog entry, e-mail processing, and even a little Web surfing. My record was 2 weeks for the entire 400+ page book.

Time Is Not on my Side

But for a deep revision, things go much more slowly. If I’m lucky, I can turn out a chapter a day. That’s a complete 20-40 page chapter, laid out with dozens of screenshots — I’m averaging about 80 per chapter right now — and captions and even a few callouts.

I just did the math. If I can keep up a chapter a day as my production rate, I should have the whole thing done by September 20. Right?

Well, unfortunately, I don’t have the next 13 days to work on this book. Next Friday, I’m flying my helicopter at the Mohave County Fair, giving rides for the whole weekend. On Monday, I fly directly to Page for two separate flying gigs over Lake Powell. I should be back by Thursday afternoon. Then the Saturday right after that, I’m hosting a photographer/writer and pilot from Australia who are preparing a coffee table book about Robinson Helicopters, featuring about 20 operators all over the world. (Can you imagine that they picked me?) When they leave, I have a few days before I head back up to Lake Powell, Monument Valley, and Shiprock with the helicopter for a group of Russian photographers for a big photo excursion.

What does this tell me?

It’s 6:26 AM on a Friday morning. I’d better get to work.

Racing with Deadlines

Posted on by
2

I prepare to buckle down and finish up a book.

After a nice, relaxing weekend at Howard Mesa, I’m back home looking at a calendar that has a deadline on it. It’s not a “drop-dead” deadline, but it is one tied in with additional financial reward. In other words, if I meet it, I’ll see more money than if I don’t. Since I’m on the downhill slide of a less-than-perfect writing year, having a few extra bucks between royalty statements would be very nice.

What makes this deadline extra important is the stuff scheduled right after it: a bunch of extremely lucrative flights for Flying M Air. In fact, I have every single weekend in October booked for an event. I also have three photo flights in northern Arizona — one of which will last 6 days.

So if I don’t finish the book on time, I won’t have much time to work on it after the deadline.

Why am I telling you this? Just so that you understand when the number of new posts drops significantly over the next two weeks. Although I’m hoping to continue to post at least one short entry a day, I might not have time to. I work best in the morning and may have to give up my coffee/blogging time to work on the book.

And, if you haven’t figured it out yet, the book in question is my Mac OS X book revision, Mac OS X 10.5 Leopard: Visual QuickStart Guide. I’m about 1/3 finished with the 744-page book. I’m extremely pleased with what I’ve done so far, but I’ll be even more pleased when it’s done.

Wish me luck!

Copy Editing – Part III: Editing for the Sake of Editing?

Posted on by
Comment

That’s what it sometimes looks like to me.

In the first two parts of this series, I told you what I think copy editing should be and told you about my experiences, over a period of 10 years, working with copy editors for the annual revision of one of my books.

In this part of the series, I’ll sum up with a few of my conclusions and observations.

Stet!Editing for the Sake of Editing

I don’t think a copy editor should make a change unless there’s an error in the text he’s editing. Error means something wrong. Not something that’s equally correct his way or the author’s. If an editor’s change does not make an improvement, it should not be made at all. Period.

This is my opinion, but I think that most people in the publishing industry — especially the authors, of course — would agree. In fact, it seems like a no-brainer.

But it does not explain the commas that have come and go with each edition of this particular book. Or numerous other changes that have not improved the book’s content. Those, I think, are edits for the sake of editing — the editor’s way of proving that he’s on the job, doing what he’s being paid to do. Almost as if he’s being paid by the edit and wants to maximize his revenue or worth.

Unfortunately for these copy editors, it’s the copy editor who understands his job and does it as instructed who will be called for the next job. My recent copy editor certainly won’t be working on any of my books again. (Most likely because the PE doesn’t want to have to deal with my complaints.)

A publisher has no need for an editor who pisses off all the authors — even if some of them are prima donnas. Who wants headaches when you’re putting together a book? Why make changes when the changes aren’t needed?

Frustrated Writers?

A lot of writers (note that I didn’t say authors here) believe that editors are just frustrated writers. The thought goes something like this: If you can’t do, teach. If you can’t write, edit.

Double-ouch!

In general, I don’t think this is true. I think some people just like to edit. They might have the skill set or patience for it. They might enjoy reading an author’s work and fine-tuning it to make it better for the reader. They might simply lack the desire to do what’s required to write a book: organize, research, compose, etc. for 300+ pages of text. That doesn’t mean they can’t do it. Just that they’ve chosen not to.

[In my case, the reverse might be true: If you can’t edit, write. My editing often comes down to rewriting. That’s not a crime if my name is on the book cover, but it is unforgivable if my only mention is fine print on the copyright page. So there’s no career as an editor in my future.]

But like other writers, I also suspect that some editors are frustrated writers. They just haven’t had the break they need to get their own work published — for whatever reason.

After all, it isn’t exactly easy for a writer to become a published author. (Again, I think there’s a big distinction here.) Sure, in the era of Web 2.0, anyone can write and be published. But it’s still a more traditional publishing process — one that involves acquisition, project, copy, and technical editors — that turns a writer into an author. And that process isn’t as easy as writing your thoughts in a form and clicking a button to publish it on a blog.

Got Something to Add?

If you’ve got something to add to this discussion, don’t be shy. Use the comments link or form to add your comment to this post so others can take advantage of your insight on this matter, too!