Tag Archives: writing

It’s a Mystery to Me

Posted on by
Comment

A little bit about the mystery novel I’ve been working on (or not working on) for the past year.

About a year ago, I started writing a mystery novel. It’s the same novel I mentioned in the entry titled “Writer’s Block Sucks” earlier in this blog. I haven’t added a word to it since then.

The book’s characters are very strong, based roughly on people I knew not too long ago. They were odd people with odd relationships, the kind of people who would be memorable in a novel. I haven’t seen these people in over two years now, but my memories of them are very clear — especially the memories about their unorthodox attitudes and behaviors. In recreating them for fiction, I changed them enough to avoid a lawsuit if the work ever got published. The similarities remain, but there’s not enough of them for any of the people to say, “Hey, she’s writing about me!” Even I’m in the book, changed enough to be barely recognizable. My character is both secondary protagonist (or sidekick) and suspect.

The protagonist or detective is completely fictional. From New York, he’s well-off and lives a comfortable Manhattan life. Yet his wealth is relatively new and he’s down-to-earth. He can mix well with all kinds of people. And the southwest town environment he’s in for this novel is a true test of his ability to adapt. His name is John and he’s a first-person narrator. In writing about the small town of Coyote Springs as seen through his eyes, I explain small, southwest towns like Wickenburg as seen by New Yorkers. It’s a view I had when I first came here, but is quickly fading as my memories of New York fade away. Part of what I’m trying to achieve in this work is to capture the wonder and disbelief I felt about the southwest years ago and document it for all time.

When I started this work, I wrote quickly with only a handful of notes to guide me. I knew who the characters were, I knew who was going to die, I knew who killed him, and I knew why the murder was committed. I also knew motives for a few other characters (red herrings). The words came quickly as I developed scene after scene. Some scenes did what they were required to do: provide background information and move the plot forward. Other scenes developed character relationships and shared information about the fictional setting with readers.

About 100 pages into the work, I stalled. And I remain stalled, to this day, right there.

A little writer’s block is normally nothing to be worried about. I’d had it before and I’ll have it again. I usually snap out of it within a few weeks, depending on what I have to write. If I’m writing a computer book, I snap out of it in a day or so — I have to if I expect to continue earning a living. But a work of fiction, with no buyer lined up for the finished product, is different. There’s no one prodding me for more pages, no one asking when the next chapter will come. There’s no milestone advance check dangling in front of me, like a carrot on a stick. There’s no real reason to finish.

But I wanted to finish this work. I wanted to try to get it published. I’d read a lot of mystery novels and I felt strongly that I could craft a story with characters, puzzle, and plot that was just as good as most of them — and better than quite a few. Still, I remained stalled.

I thought about what had gotten me started in the first place. It was a combination of things. One was the idea of killing someone I couldn’t really kill. No, I couldn’t murder someone I didn’t like, but I could, in writing, tell the story of how a fictional representation of that person was killed. And, along the way, I could entertain and educate readers. And write something other than computer how-to books and articles.

The other thing that motivated me to begin was a Stephen King book. No, it wasn’t one of his horror books. Although I was a big fan of Stephen King years and years ago — when his first novel, Carrie, came out, in fact — I hadn’t read any of his work in years. But while browsing the bookstore shelves, I came across a nonfiction book he’d written: On Writing. I bought it and devoured it (with my eyes, not my teeth) in just two days. It was an excellent motivator for me. It told the story of how he’d gotten started and the way he works. It then provided guidance for writers that didn’t talk about grammar or usage or any of the nonsense many writer’s guides go into. (If you can’t structure a sentence, you shouldn’t be a writer.) The other thing conspicuously missing from the book: exercises. Stephen King wasn’t leading a “how to write a novel” course. He was telling the reader about his experiences and what he thought worked. And, given his record, that’s something worth reading.

When I finished On Writing, I felt charged up and ready to go. And I did. I wrote about 100 pages in less than two weeks. But that was it.

I tried to analyze the problem. I knew I had scenes to write, but I was worried that the plot wasn’t progressing at a fast enough pace to keep the reader interested. I felt that the problem I was posing was too easy to solve, that the murderer would be too obvious. I made notes about other character relationships, building stronger motives for other characters. And when all that thought and note-taking didn’t help, I hopped onto Amazon.com, shopped around, and bought a few more books about writing. I hoped that some of them would motivate me.

Among the books I bought were books specifically about writing mysteries. I read a few of them right away. One of them said something that chilled me to the bone. It said that if you wrote without being fully prepared, you’d get about 95 to 100 pages into your story and stall. At the time, I didn’t know how far I’d gotten, but I whipped out my laptop and checked. 98 pages. Sheesh. How did he know?

All the books made one important assumption: that the murder had been committed before the novel opens. In fact, they all seemed to assume that the story opens at the scene of the crime, with the body still in place.

My mystery doesn’t start like that. In fact, 100 pages into the novel, the victim is still alive. I’ve been giving that a lot of thought. Why isn’t he dead yet? Why haven’t I killed him? My conclusion: I’m developing his character along with the others. I want the reader to feel like I do: that he deserves to die. But in reading these how-to books, I realize that may be a mistake. To make a reader care about solving the murder, you have to make him care either about the victim or about clearing the name of a suspect he likes. Although I’m establishing one character as a likable suspect, one that the reader doesn’t want to see as guilty, I shouldn’t waste pages making the victim so unlikable.

In looking at my notes, I realize that at least another 50 pages will go by before my victim dies. That’s something I need to fix.

Years ago, I had a friend who was passionate about becoming a fiction writer. She wrote short stories, novels, and other works of fiction after work. She frequented writer’s message boards on BBSes (before Internet mailing lists), and spoke up about what she believed. Unfortunately, she didn’t have a very good attitude about the business of writing. In her mind, editors were evil and their sole purpose in life was to destroy the work and moral of writers through extensive editing and rejection. When she quit her job to write full-time, I knew what the outcome would be. I was right: a year later, she was deep in debt and still hadn’t sold a single piece of work. I don’t know where she is now or what she’s doing, but I’m pretty sure she’s not making a living as a writer. Yet there was one thing I remember her saying, one piece of advice that I can’t argue with: “If you can’t go forward, go backwards.”

I don’t know if I understand that statement the way she meant it, but it does make sense to me. If you can’t continue a story, there must be something wrong with what went before it. Go back to previous pages and examine them. Where did the plot take the wrong turn? Tear out the bad pages and write new ones.

The idea of discarding something you’ve written is sometimes referred to as “killing your darlings.” It’s a fact of life: when you write something, you often fall in love with it. It’s difficult to discard it, never to use it again. But a real writer — a professional who cares about the final product — shouldn’t be so in love with her work that she doesn’t edit out what doesn’t work. So I need to do some editing.

I have a plan of attack on my novel that isn’t fully fleshed out yet. Basically, I plan to ruthlessly cut away scenes that aren’t moving the plot forward. Some of them can be salvaged. For example, there’s a scene where John is taken on a tour of the ranch. Later, he takes a horseback ride that covers some of the same territory. Some of the places he sees on both trips are important later in the novel. But do I need to talk about them twice? No. I can cut out his first tour and keep the later one (not written yet). I can use some of the descriptions I’ve already written when I write the new material.

Another goal: kill the victim by page 50. Now I know I just told you that all the how-to books say the book should open at the murder scene with the victim already dead. But I’m not writing a murder mystery that’s just a puzzle for the readers. My story is also in entertain and inform. To do the job properly, I need to develop relationships between characters. And I can’t do that if one of the main characters is dead. Besides, I believe that by bringing the narrator into the story before the murder, I’m giving readers a clearer vision of what the events leading up to the murder are. They see what’s going on because the narrator sees what’s going on. The facts aren’t brought forward solely by the detective having question and answer sessions with witnesses and suspects. Instead, the reader is in on the plot.

Besides, I’ve read plenty of mysteries that started out with a live victim, so there’s obviously more than one way to get the job done.

But although I write for a living, I don’t write mystery novels for a living. That means I need to take care of my day job — writing computer how-to books and articles and building a helicopter tour business — first. To further complicate my life, a tenant recently trashed a rental property I’m trying to sell, and I’ve been spending a lot of time there, cleaning up her mess and dealing with contractors. So I don’t think I’ll be writing much more about Coyote Springs over the next week or two.

But I’ll be thinking about it, and that’s the most important part of writing any complex plot.

Freebies

Posted on by
1

On why a professional writer should consider writing for free.

It was a hotly debated topic back when I started writing professionally and frequented BBS message bases (the precursors to Internet mailing lists). Some people argued that a professional writer should never write for free. In fact, one person even bragged about how much free work he turned down regularly. (Of course, he never bragged about the paid work he got, either.) Other people — including me — argued that to break into a writing career, you have to write for free, at least in the beginning. How else would you get the clips you need to establish yourself as a writer?

Clips are the beginning writer’s Holy Grail. A clip is an article or a story you have written for a magazine or other published document that has been “clipped” out to show other publishers or editors you want to write for. It’s proof that you have been published. The more clips you have, the more experience you can prove. You can then use those clips to impress the people who can get you better assignments.

Of course, the quality of a clip is just as important as the overall quantity of clips. A clip from, for example, Vogue, is worth about 50 clips from small press beauty newsletters that no one has ever heard of. So the argument that you should be paid for all of your writing does have some merit, since Vogue is far more likely to pay for your work than the sporadically published Betty’s Beauty News (if such a thing exists).

Back when I started, I was breaking into a new career that I had absolutely no formal training for. Heck, I was a financial analyst and former auditor with a degree in accounting! What did I know about journalism? I knew enough, it seems.

I knew back then that I needed clips to get started. I knew that no one would pay an unknown to write for them. So I knew I had to write a few freebies. And I did.

My first published article was for The Audit Advisor, a 12-page monthly newsletter for auditors, back in 1987. It was an article about auditing construction project budgets. I received two copies for my efforts. No money. But I had my first clip.

I wrote a few other articles for publications I can’t remember. Junky little publications. One was a writers’ newsletter. When I received my sample copy, I was appalled that my work had appeared in such a rag. It had obviously been “printed” on a photocopier. One that needed maintenance.

I got my next big break in 1989, when the Institute of Internal Auditors (IIA) offered me $10K to write a 4-1/2 day course about using computers for auditing. I had taught a few times for them — also for free, with permission and salary from the company I worked for at the time — and knew what they were looking for. I was also quite informed about personal computers, which were very new at the time, and how they could be used to simplify work while performing a financial audit. I asked for leave of absence from work, but they wouldn’t give it to me. So I resigned my $45K/year job (a huge amount of money in those days) and took the biggest gamble in my life: to start a new career as a writer.

I finished the course in the alloted amount of time and even taught it a few times for the IIA. They paid me to write spinoff products for it. I can’t remember what they were, but I have copies in my office somewhere. But I was not really a writer yet. I hadn’t paid enough dues, I didn’t have enough clips for what I wanted to write about: computers.

So I got to work and found some more small publications to start writing for. For free. One of them was one I cooked up: Macintosh Tips & Tricks. It was a monthly newsletter that lasted a few years in a number of formats. People paid to get it mailed to them, so I guess you can say I was being paid for my writing. But not enough.

So I supplemented my income with a job as a per diem computer trainer. I worked for two different companies. One paid pretty well; the other paid very well. It kept the mortgage paid and food on the table.

Oddly enough, my next big break was as a ghostwriter for a John Dvorak book. Dvorak was very big in the computer world back in the early nineties and his name sold books. So the publisher, Osborne/McGraw-Hill, had hired him and Bernard J. David to write a book called Dvorak’s Inside Track to the Mac. Of course, they didn’t actually write the books. They hired ghostwriters to do it. They split the chapters and farmed them out to a handful of people who were probably a lot like me: struggling to get started as writers. I got the Fonts chapter and finished it quickly. Bernard liked it so much, he gave me three more chapters. I made a whopping $500 per chapter. My name doesn’t appear on the cover, but it is in the second paragraph of the acknowledgments. A very big deal in those days.

I neglected to mention how I managed to make this connection. This is an odd story, too. I’d written a book proposal about using Macs for Telecommunications. I was rejected by the four or five publishers I sent it to. (Ted Nace at Peachpit Press wrote a kind letter saying that there wasn’t a big enough market for the book. The truth is, I was ahead of the time back in those days. A year later, telecommunications really took off.) But one of those publishers sent my proposal to an agent. The agent wanted to represent me, but I was unproven. (Not enough clips.) So he referred me to Bernard who wasn’t terribly pleased (at first) about having to give me a chapter of the book. The really odd part about it is that the agent never contacted me again. To this day, I’ve never been represented by an agent.

After that book, Bernard wanted to work with me again. We wrote The Mac Shareware Emporium for Brady Books. It didn’t do very well, primarily because another book on the same topic was published two months sooner (for reasons I won’t get into here) and it was heavily promoted on AOL. (AOL was just starting to gain momentum at the time and shareware was hot.) But I did have the ultimate clip: my name on the cover of a book.

Fast forward to today. Since leaving my full-time job, I’ve written or co-authored about 60 books. (Many of those are revisions to existing, long-lived titles.) I’ve also written hundreds of articles for magazines, newsletters, and Web sites. My published books collection (including translations) fills three shelves on a bookshelf and my clips, which I don’t even bother collecting anymore, fill a file storage box. You can see a list of everything I’ve bothered to list on my Web site’s Books and Articles pages.

So you might assume that I no longer write for free. Not so. I’m obviously writing this for free. (No one is going to pay to read the things that go on in my head and in my life.) And until recently, I wrote how-to pieces for publication on the Web.

Why? Well, the way I see it, there are two goals to writing. One goal is to make money. That’s why I expect to be paid for writing books and most articles. I have to earn a living. But the other goal is to establish yourself as an authority and spread your name around so people will look for the other things you’ve written.

For example, suppose I write an article about Faxing with Mac OS X Panther. The article gets read by a bunch of people. Some of them may have read other articles I’ve written. They like my writing style, they feel I know what I’m talking about, they think they could benefit from reading some of my other work. Like my books. So they go to the bookstore or log into Amazon.com and buy a book. And I just earned a little bit more money on book royalties. While it doesn’t really pay to have one person do this, it would be nice to have a thousand people do this. And with Web publishing, this is possible.

If you were reading carefully, you may have noticed that I used the phrase “until recently” when mentioning that I wrote how-to pieces for publication on the Web. I still do write these how-to pieces, but I’ve found Web sites that are willing to pay for them. So instead of writing them for free, hoping that readers will buy books to compensate me for this work, I can now be paid for the article. And one of these Web publishers is kind enough to put links for buying my books where the article appears. So a reader can succumb to impulse buying and order the book right then and there.

Will I still write how-to pieces for free? Yes. But only when I can’t write the same pieces for paying markets. After all, I do have to make a living. And the clips box is full.

Do It Yourself Layout

Posted on by
2

How and why I lay out my own books.

I do layout for most of my books. That means I submit finished pages to my editors. What they see on the page is what the book will look like when printed.

I write the book as I lay it out, in Adobe InDesign CS. InDesign is an incredibly powerful page layout program, but I use only a fraction of its features. I start with a template that has all the elements of page design. I use text boxes to position text in the appropriate place. I actually type the text right into the text box — I don’t use InDesign’s separate text editing window. I use styles for paragraphs and characters. I’ve even taken advantage of InDesign’s nested styles to automatically format text like numbers in numbered steps and bullets in bulleted lists. That saves a lot of time and ensures consistent formatting.

I create figures using screenshot software on my “test mule” computer. That’s the computer I run the software on while I write about it on my production computer. My Macintosh test mule is an eMac; my Windows test mule is a Dell Dimension PC. Both are networked to my production computer, a dual processor Macintosh G5. I pull the screenshots over to the G5, open them with Photoshop, and run an action on them to convert them to grayscale (or CMYK, depending on the book) and save them as uncompressed Macintosh-format TIFF files with 72 dpi resolution. Then I literally drag the image icons from a Finder window to the InDesign document. I downsize them to fit, which also enhances resolution, and drag them into position. Then I use InDesign’s library feature to insert a pre-formatted caption, which I fill in for each screen shot. This is probably the most time-consuming part of layout. No, that’s not true. Callouts — those little lines that run from labels to exact positions on a screen shot — take far more time to do. I have InDesign library elements for other items, too, like thumbtabs (for my Visual QuickStart Guides) and callout lines (for my Visual QuickPro Guides).

I write each book a chapter at a time. When a chapter is finished, I create a PDF format file of its pages that includes printers marks such as registration marks and cut marks. (Can’t remember the exact names of these things.) I then upload the PDF file to an FTP site where my copy editor and production editor can download them. There’s a workflow over at my publisher’s place that varies depending on the editors assigned. What I see at the end of the process is printed pages that have been marked up by both editors. I get them a few chapters at a time via UPS. I normally take care of the edits in the afternoon, after submitting a chapter for the day. (I try to do a chapter a day for revisions and a chapter every two days for new titles.)

I review the edits and make about 98% of the changes that are requested. Most changes are of a typographical nature — I have a habit of repeating words and leaving characters out of words — but some are of a layout nature — rewrapping text to prevent widows, moving a callout up two points to improve spacing, etc. And of course, there are always a few grammatical errors that need fixing. (I wasn’t an English major!) Any time I don’t make a requested change, I note the reason why on the marked up pages. I don’t ignore a change without good reason. Then I print the manuscript and send it back to the editor with the markups. If the production editor is a freelancer, I usually have to print up a second copy for him or her. It usually takes about 30 minutes to turn around edits for a chapter, so I can knock them off quickly. The final InDesign and TIFF files get FTPed to the production editor or, if he or she requests it, put on a CD. The production editor sometimes puts a few finishing touches on the final files.

When I finalize a chapter, I also create a finalized PDF and upload it to the FTP site for the indexer. Sometimes, if the book is on a tight deadline, the indexer will work on draft pages. This is usually pretty safe, especially for revisions, since pages rarely have significant changes from draft to final. When the indexer has indexed all chapters, she submits a Word or RTF file to me via e-mail. I then pour the index into an Index template and reformat it to fit the number of pages allotted. Sometimes that means making the font size really small — my last book had 7.2/8.2 font for index entries. Other times, that means making font size and leading normal but increasing the spacing between paragraphs or above headings. The book’s total page count has to be evenly divisible by 8, and it’s my job to make sure I submit exactly the right number of pages. Fortunately, Peachpit is not normally page count driven. A book can be as long or as short as it needs to be — as long as the total number of pages is divisible by 8. That’s great for me, because I can write just what I need to.

Generally speaking, it takes about a week from the time I finish all chapters in my first draft to the time the final files and index are ready to send to the printer. It then takes about three weeks from the time the files get to the printer to the time I see a printed copy of the book. Add another week for copies to get to stores and you have a 4-week turnaround from finished manuscript to book available in stores. Obviously, this is the greatest benefit of doing my own layout. Let’s face it, computer how-to books are extremely time sensitive. To get a book out quickly, you have to prepare it quickly. I have a knack for doing my job quickly and since I don’t have to depend on someone else at the publisher to do time-consuming layout, each book can be turned around very quickly.

There are other benefits to doing my own layout. It’s great for me because I have a lot more control over my work and can write in a way that takes advantage of the book’s layout. I also get a bit higher royalty rate to compensate me for my additional work and the cost of labor I’ve saved my publisher. It’s great for my editors because they can see the “final” product as they are editing. So if the layout isn’t quite right — for example, a figure would be better on one page than another or could be improved with a callout — they can tell me and I can fix it as part of the editing process. Otherwise, the book would have to go through multiple editing processes, each of them handled by someone different who may or may not care about the quality of the book. I’m the author of my books and I care about all of them, so I do my absolute best to make sure they’re something I’d be proud to have my name on.

Peachpit, to my knowledge, is the only publisher that allows authors to handle what they call “packaging.” And they won’t let all authors do it. You have to prove that you have the ability to handle layout to their standards. I’ve been doing layout for my own books since 1996 and have produced over 40 titles for them, so I’m proven.

Other publishers don’t work this way at all. In fact, they are completely opposed to the suggestion that an author layout out the book. The reason: they are worried about losing control over the book’s contents. They don’t seem to understand that they do get final possession of the manuscript’s files and can make any changes they like before sending the manuscript to the printer.

One of my other publishers, in fact, has an extremely complex production process. First the author writes the manuscript using a Word template that has macros built in for formatting. Some of the macros work, others don’t. The author is required to insert special codes in the manuscript to signal certain types of styles. Meanwhile, the author creates screenshots, which are supposed to be submitted as full screen images. The author is supposed to print each one and mark where the image should be cropped. (I refuse to do that because it wastes time and paper and relies on a production person to get the cropping right. I send cropped images and I don’t even bother printing them anymore. Nobody complains. Frankly, I think they’re relieved that I’ve spared them this extra work.) From the author, the Word file and images go to a copy editor and a technical editor. The copy editor uses Word’s change tracking feature to mark up the manuscript and insert all the codes the author has either neglected to insert or inserted wrong. The Word file then goes back to the author for review. The author further messes up the file by using the change tracking feature to accept or reject changes. The author also gets comments from the technical editor and changes the Word file to make necessary corrections. A production editor gets it next and incorporates the copy editor and author changes to finalize the file. Then it goes into production, where it’s converted into a Ventura Publishing file (I kid you not) with the images inserted. The images are usually in-line images, meaning that text doesn’t wrap around them. It also means that the images might not appear where the author thinks they should. (But that doesn’t seem to matter much.) The author gets “proofs” of these pages, in print, and is required to mark them up and send them back to the publisher. About 10% of the author’s suggestions are incorporated into the final pages. To be fair, any change that corrects an error goes in but any change that tweaks the layout is basically ignored. The book eventually makes it to the printer where it is printed and sent out. Time elapsed from completion of first draft to printed copies: 8 to 12 weeks.

Is the quality of a book better when a professional publishing staff takes it from manuscript draft to printed book than when an author takes it most of the way? I don’t think so. But I also think that quality isn’t the most important aspect of book production to some publishers. But that’s a topic for another blog entry.

Books of 2004

Posted on by
Comment

I bring readers up to date with the titles I churned out over the past year.

I realized, in writing my last blog entry, that the last book I’d mentioned finishing on these pages was my Mac OS X 10.3 Panther: Visual QuickStart Guide last October. Don’t think for a minute that I’ve been idle since then.

It’s been just over a year and, believe it or not, I had to consult a list of the titles I’d put out to see just what I’d been up to. I just couldn’t remember them all. Here they are:

Microsoft Office Excel 2003 for Windows: Visual QuickStart Guide was the most recent revision of my Excel for Windows book. Not much new in the way of content because there’s not much that Microsoft can already add to that feature-packed program. It came out in December 2003.

QuickBooks Pro 6 for Macintosh: Visual QuickStart Guide was a brand new title for me (and Peachpit). I’d proposed it early in the year, when I was looking for work and it took several months for them to say yes and come up with a contract. By that time, I had other work lined up. (Feast or famine.) The book underwent a lot of content changes as I wrote. For example, it was originally going to include payroll coverage, but since payroll is done with a separate program bundled into QuickBooks and the future of the bundling was questionable, we decided to drop it. (Frankly, I think payroll is so confusing that a whole book could be written about it, but don’t think I’m volunteering.) The book came out in May 2004 and is doing surprisingly well. So well, in fact, that Peachpit wants me to revise it for the recently-released new edition.

Quicken Premier 2005: The Official Guide is the sixth revision to my original Quicken Official Guide. It was finished in June 2004 and published in August 2004.

Creating Resumes, Letters, Business Cards, and Flyers in Word: Visual QuickProject Guide was a brand new title in Peachpit’s brand new Visual QuickProject Guide series. The series is great for beginners or people with computer phobias because it shows every single step in a process, with callout lines and numbered instructions. It makes a VQS look like a technical guide for MBAs. And it’s in full color! It’s 160 pages long and costs only $12.99. A great deal. The only thing I don’t like about it is the title — it’s way too long! It came out in September 2004.

Creating Spreadsheets and Charts in Excel: Visual QuickProject Guide is another brand new book for me. This one offers the basics of working with Excel spreadsheets and charts in a format anyone can understand. It’s eight chapters took me eight days to write and lay out. (That’s not the record. My record is a 350-page book that I knocked off in 10 days back in 1993. Of course, I didn’t do layout for that title.) I think it’s a great book and I’m extremely pleased with the way it came out. Like the Word book, it’s cross-platform. It came out in October 2004.

Microsoft Word 2004 for Macintosh: Visual QuickStart Guide is the latest revision to my Word for Macintosh book. It has a bunch of new stuff inserted throughout the book and a brand new chapter covering Word’s new Notebook Layout view feature. I finished it two days ago and it’ll go to the printer today. I expect to see it by the first week in December and, of course, it’ll be at Macworld Expo.

So in the course of a year, December to November, I finished six books. Of these, three were revisions and three were brand new titles. (That’s not a record. My record is 10, set a number of years ago, and I hope I never do that again. Talk about burnout!)

In addition to writing all those books, I also managed the Wickenburg Airport’s FBO (for a short time, anyway), did helicopter tours in the area, got a part-time job flying at the Grand Canyon, and wrote a handful of articles. So anyone who says I have an easy life obviously doesn’t have the big picture.

I’m not complaining — certainly not! I usually take a week or two off between books and spend that time catching up on things like bills, surfing the ‘Net, shopping, and writing in my blog. If I had a helicopter, I’d be flying, but I’m between ships right now and grounded. This week, I’m trying to write three or four articles that I owe various editors. I knocked off one yesterday and started a second one. I’ll finish that and write at least one more today. Tomorrow, my brother, his wife, and my sister are coming in for a week, and my mother and stepfather are showing up on Tuesday for a week, so I’ll spend time with them.

Then it’s back to the salt mines for me. Mac OS X 10.4 Tiger is on its way and I have to revise the existing book to turn it into Mac OS X 10.4 Tiger: Visual QuickStart Guide. I always have the first Mac OS book out in stores and I’m not about to ruin my record this year.

After that, it looks like a QuickBooks revision, but if I’m lucky, they’ll let me write one or two more Visual QuickProject Guides. I proposed a bunch of titles, and they finally seemed to like one of them. Cross your fingers for me. I’m also writing an eBook about iBlog 2.0 for Spiderworks. I’ll probably finish that sometime in December, if I can find time for it between my work on the Tiger book. I’m also working on a book about the Grand Canyon with a photographer and hope to have that ready for publication in May. It’ll be nice to have a book that doesn’t need revising every one or two years. (The Canyon doesn’t change much.) And I’ll always be writing articles. Informit.com likes my work and I like writing for them. FileMaker Advisor also wants me to write for them, but I’m always having trouble coming up with fresh ideas for them, so we’ll see how I do.

That’s it in a nutshell: the past year and the next four to six months. Busy, busy, busy.

Busy Busy Busy

Posted on by
Comment

I realize that I’ve been so busy that I haven’t made a blog entry in nearly a week.

I’ve been busy this past week. Too busy to write in my blog.

I’ve been working hard on my latest book, Microsoft Word 2004 for Mac OS X: Visual QuickStart Guide. I was moving along at a pretty good rate — about a chapter a day. I expected to finish it on Friday, but a sudden storm moving in sent me home early that day. I arrived home to get the horses out of their lower corral in the wash just as the water started flowing. So I finished it today. This afternoon and tomorrow, I’ll be going through the edits. The index should arrive from the indexer on Thursday. The book goes to the printer on Friday. I’ve lost count again, but I think this is either my 59th or 60th book. I dedicated it to Ted Waitt, my editor on this project. I’ve kind of run out of people to dedicate books to.

The book has a picture of Ted in it, too. Chapter 17, I think. I don’t remember the page number. There are a few other interesting photos in there, including the one Bert Monroy helped me cook up for Flying M Air marketing materials.

Speaking of that, the postcards I ordered arrived and they look absolutely fabulous. I spent part of today distributing them around town. I picked up the slides last Monday and dropped one of them off at the movie theater when we went to see The Incredibles. (What a really great movie!) It should be in the tray by now.

I also talked to my editor at Informit and she’s very interested in getting some new articles from me. I told her the best time to get work from me is between books, so I guess I’ll have to start producing this week. I figure I’ll knock off 2 to 4 articles for her. I also have to write one for FileMaker Advisor.

Vertical wants to publish my jumper article. I had a nice conversation with the publisher, Mike Reyno, the other day. But I’ve spoken to the folks at Papillon and they’re not too happy about the article coming out. So I’m not quite sure what to do. I certainly don’t want to piss them off.

I ordered and received some Robinson R44 materials, including a maintenance manual, parts catalog, and passenger briefing card. This is all stuff I need for my Part 135 certificate. I haven’t done any work on that since my meeting at the FSDO last Monday.

Today I stopped by Kwikprint to get a tabloid-size document printed (my printer doesn’t print on paper that big). Later I went back with a new order for business cards and letterhead. With luck, that’ll be ready by next week.

On Sunday, I met someone who has read all of my blog entries. She’s married to someone Mike works with down in Phoenix. She and her husband and his mother came up to Wickenburg for the Bluegrass Festival at the rodeo grounds. I didn’t go with them. I’m not much of a bluegrass fan. Anyway, she already knew what I looked like from photos in my blog. She talked to me a little about my entries. It was kind of weird. I didn’t think anyone read what I wrote here. She’s probably reading this right now!

Hello Barbara!

Right now, as I write this, I’m listening to a live audio stream from JFK Ground/Tower. You can listen online via a link on www.liveatc.net. JFK tower is kind of cool because the controller has an unbelievable New York accent. It’s like being back there again. I didn’t think it would work on my Mac, but when I clicked the link, it automatically opened in iTunes and started playing. Way cool.

I also spent a few minutes bothering my brother via MSN Messenger. Why people use chat software when they can just pick up the phone is beyond me. My brother types very slowly. I’d much rather talk to him on the phone than wait for him to type messages to me.

He and his wife and their dog are coming with my sister on Saturday. My mother and stepfather arrive on Tuesday (next, not tomorrow). They’re all coming for Thanksgiving Dinner. So I have to get all my work done this week so I can spent the whole week with all of them.

Two days after all of them leave, Mike’s mother and her friend come for 10 days. Then it’s his turn to do the entertaining. I have to start another book.

Busy busy busy. No wonder I’m so tired at the end of the day.