Tag Archives: careers

Leopard Postponed — What's a Writer to Do?

Posted on by
3

It’s all about timing.

Yesterday afternoon, not long after the stock markets closed in New York, Apple put a one-paragraph announcement on its Hot News page. The announcement told the world (or whoever happened to be watching that page) that because Leopard resources had been used to finish up the iPhone, Leopard would be delayed. Instead of seeing the finished OS in June, we’ll now see it in October.

Why it Matters to Me

I took the news with mixed emotions. I had begun working hard on my Leopard Visual QuickStart Guide for Peachpit Press. The book will be the eighth or tenth (I’ve lost count) edition of my Mac OS VQS, which is one of my biggest selling titles. The book is important to me; the last edition accounted for half of my annual income for two years in a row. When that book is ready to write I drop everything — even helicopter charters — to work on it.

The most important part of it is getting it done on time. When Tiger came out in 2005 only two authors had books in stores beside the brand new software on its release date: Robin Williams and me. Both long-time Peachpit authors with reputations for churning out books that satisfy readers. If Robin’s book sold only half as well as mine — and I’m not fooling myself; it probably sold twice as well — we kicked butt. It was a great reward for hard work and grueling deadlines. But I have to say honestly that my Tiger book was one of the ones I’m most proud of.

This Time was Different

This time around, things were definitely different. The software wasn’t ready yet — that was obvious in the way certain features just didn’t work right. Lots of bugs to iron out, but few developmental releases. It was almost as if Apple’s Mac OS team was overwhelmed. This announcement from Apple explains a lot. Apparently they were overwhelmed, but not by the task at hand. They were overwhelmed by being shorthanded to tackle the task at hand.

Add to that the fact that my screenshot software of choice, Snapz Pro, “broke” in Leopard. Don’t misunderstand me; it did work and it took fine screenshots. But the shortcut key to invoke it did not work — even when I fiddled with Mac OS settings and tried other shortcut keys. So, for example, there was no way to take a screenshot of a menu.

I don’t know if you’ve ever seen a Visual QuickStart Guide, but they rely on screenshots to communicate information. The book is full of step-by-step, illustrated instructions. I estimate that my Tiger VQS has at least 2,000 screenshots in it. Some screenshots show windows, others show menus. Almost every single one is less than a full screen of information. Now think of how much fun it might be to take 2,000 screenshots with something as awkward as Grab or, worse yet, Apple’s built-in screenshot shortcut keys. And then manually edit every single screenshot in a graphics program like Photoshop. Not having Snapz Pro (or something equivalent, if something equivalent exists) was going to seriously slow down my workflow.

What was even worse for me (and all other writers, I assume) was the “secret features” Steve Jobs alluded to when he first showed off Leopard. I had no idea what they were. And no one else did either. What if those features changed the way part of Mac OS X looked? All my screenshots would have to be redone. And what if the features were big enough to warrant their own chapters? Or replaced existing features? That could mean significant reorganization of the book, with changes to all the chapter and feature references. I could be working my butt off to finish a 700+ page book, only to have to redo major parts of it.

So I was under a lot of pressure. I had the ticking clock that said the software would be out “this spring.” That meant before June 20. I knew my publisher needed 2-3 weeks to get the final files printed and turned into books. That meant I needed to be done writing and editing by the end of May. But not knowing what the future would bring, was crippling me, making it difficult and frustrating to get things done.

I was not a happy camper. So when the announcement came yesterday, it was a bit of a relief for me.

The Problem with the Postponement

There is a problem, however: timing.

I had planned to work on my Leopard book for April and May. Then comes my annual secret project (which I can’t talk about until after publication) for the month of June and a bit into July. Then my annual one-month stay at Howard Mesa to get some work done on our property and knock off a few articles for Informit and possibly try to reconstruct that mystery novel I was working on (which was lost in the great hard disk crash and backup screw-up of February 2007). Then we’d planned to take a vacation to the northwest to continue our search for a new place to live. By that time, it would be September and the helicopter business would be heating up again; I already have two charters lined up for that month. Also, around that time, I’d be ready to start work on my Word for Macintosh revision.

There was a plan B for this summer, too. It consisted of me getting a job as a pilot for someone else, flying somewhere other than Arizona. I could work on my secret project while I was away and escape Arizona’s brutal heat and get to fly someplace different. I have a very good lead on a job in St. Louis (of all places) and a few possibilities in Oregon and Washington. But nothing finalized.

Now these plans for the next six months of my life are completely up in the air. Assuming an October 1 release of Leopard — this is just a date pulled out of the air; I swear I don’t know anything and if I did I wouldn’t repeat it — I have to be finished with the book by the first week in September. So I’ll work on it in July and August. While I still have my secret project to work on in June, I don’t have anything lined up for the rest of April and the month of May.

What’s even worse about all this is that I can’t work on a VQS at Howard Mesa or at a summer job elsewhere — I need a desktop computer with a big monitor to do the layout — and I can’t take a vacation when I need to work on this book. (See above for how important it is.) So my whole summer schedule is completely screwed up.

And It’s a Money Problem, Too

And since I get paid advances when I work and I don’t have anything lined up between now and the beginning of June, I’m not going to see a payday until the end of June or July. Ouch. So my finances will be screwed up, too.

It gets even worse. If the book had a release date in June 2007 (with the original release of Leopard), I’d start seeing royalties at September 2007 month-end. But because it won’t be released until October, which is after the start of the last quarter, I won’t see royalties until March 2008 month-end. That’s a 6-month payday delay for a 4-month publication delay. Double-ouch.

But that’s what the freelance writer’s life is like: a financial roller coaster.

What to Do?

Today I’ll be making some phone calls. The goal is to pin down exact dates for all of my known projects so I can decide, once and for all, if I can get a pilot job according to Plan B. And, while I’m at it, I’ll try to pick up a small book project to work on in May. (Not likely but remotely possible.)

Then I’ll get to work doing other things that I’ve been neglecting — cleaning out the condo I want to rent, washing the helicopter, organizing my office, reserving rooms for next year’s Southwest Circle Helicopter Adventure trips.

After all, life goes on.

The Helicopter Job Market

Posted on by
207

It’s pretty shameful.

Knowing how to fly a helicopter isn’t exactly a common skill.

It takes at least 40 hours of flight time to get a private license, although most people need at least 60 to pass the check ride. At at least $200/hour, the cost alone is enough to scare most people away from learning.

Then, to get a commercial license so you can do it for hire, you need 100 hours of pilot in command time (at about $200/hour if you rent) and to pass yet another, more stringent check ride.

So then you can get a job, right? Not quite. No one is going to hire a 150-hour pilot to fly their helicopter with paying passengers aboard. In fact, you probably won’t be able to find a job flying for someone else until you have at least 1,000 hours of pilot in command time.

How do you build that time? Most people do it by becoming a flight instructor or CFI. That’s more training, more requirements, and another check ride. Then shamefully low pay rates — maybe $15 to $25/hour? That might sound good, but we’re not talking about a 40-hour work week. You get paid based on when you teach. That might be 10 or 20 hours a week. I don’t know too many people who can live on that.

(I did it the more expensive way. I bought a helicopter and flew the paint off it. Figuratively, of course.)

Captain MariaSo now you’ve got 1,000 hours of PIC time, accumulated over a period of about 2 to 3 years. You’re ready for a “real” job. Fly tours at the Grand Canyon (like I did). It’s great experience, but the pay is only slightly better than what a CFI gets. Fly in the Gulf of Mexico, bringing oil rig workers and VIPs to and from platforms on a featureless, watery landscape, miles from land, in good and bad weather. More good experience, slightly better pay. Pretty crappy living conditions, from what I hear. And I don’t think many women work out there. (Would love to hear from a woman who does; use the Comments link.)

Want a high paying job? One of those $80,000/year job you hear about on radio commercials and in seminars? You’ll need several thousand hours of turbine helicopter experience (which you usually can’t get as a CFI), long line experience, and a “OAS/USFS card.” You’ll have to work your way up through the ranks on other kinds of helicopters to get to this stage.

And, oh yes, you have to be willing to be away from home at least 14 days out of every month.

My friend, Rod, is among the handful of people who qualify for the good paying jobs. He does all kinds of long line work — logging, fire fighting — you name it. But the long hours, questionable living conditions, and time away from home burns him out so badly, he can only work half a year. He actually spent a winter delivering propane (from a truck) just to get away from flying.

Think I’m lying about job requirements? Check out these links for helicopter jobs:

Even police helicopter pilot jobs start at less than $50K. And they require police training, too.

And I think that’s amazing. Helicopter pilots have an incredible skill that few other people have. They have thousands of dollars and hours invested in their training and experience. They’ve worked their way up from the bottom, with low pay and unfavorable working conditions most of the way. And only a handful will ever achieve the high pay you’d think would come at the end of the dues-paying process.

I’m fortunate enough to have two jobs, so I never have to depend entirely on helicopter pilot pay to cover my living expenses. Still, that tour pilot job in Hawaii remains beyond my reach — until I get another 650 hours of turbine time…

On Geniuses

Posted on by
6

Why I don’t Genius Bar hop and other comments regarding my recent hard disk problem.

One of my jobs as a blogger is to produce at least one blog entry a week. As you may have noticed if you follow this blog, it looks like I’ve been slacking off lately. Well, I just want to take a few moments to assert that looks may be deceiving.

Last week was a busy one for me. I finally got my computer back up and running after its second hard disk crash in a year. This crash was far more serious than the last and required the geniuses at the Apple Store to fix.

Now I know that lots of Mac pros laugh at the word “genius” when applied to the Apple Store’s tech support folks. And I do agree that it would be difficult to call any of them geniuses in the true sense of the word. (Think Einstein.) But if you were to compare their computer skills to the average Mac user’s, they could indeed be considered geniuses. They know a lot more about the current computer models than 95% of Mac users. Sadly, I fit into that 95% these days. I could tell you all kinds of things about fixing a Mac II cx or a PowerMac 7100/66 — and that’s because I used to teach a course about troubleshooting those computers running System 7. Nowadays, my troubleshooting capabilities are limited to what I need to know — like much of my other knowledge — and I don’t really need to know all the things the geniuses need to know to do their daily fix-it jobs.

So I’m not uncomfortable applying the word genius to many (but not all) of them. To me, some of them really are geniuses when it comes to diagnosing and fixing Mac problems.

I’ll also be the first to say that the capabilities of an Apple Store genius staff on any given day for any given store is hit or miss. It all depends on each staffer’s experience, knowledge, and interest in the topics he or she needs to know. I was at the Genius Bar in the Chandler, AZ store on Monday and the geniuses that day were pretty good. One of them was a super genius, the one who helped me was definitely above average, and the guy working the iPod slot was about average. (Let’s face it: it doesn’t take much skill to fix an iPod problem. Every iPod should come with a cheat sheet printed on back that explains how to reset it; that will resolve 95% of an iPod’s problems. The iPod guy probably resets a lot of iPods in a day. I’ve gotten so good at it that I can reset mine with one hand while flying my helicopter. Darn vibrations lock it up more often than I’d like to admit.)

I’ve had repeatedly bad luck at the Biltmore Apple Store in Phoenix, which is at least 30 miles closer to my house. The two times I tried to get assistance there, the lead Genius didn’t seem interested in looking deeply into my problem and didn’t seem to care whether it was resolved or not. On my fried motherboard problem, it seemed that she spent more time telling me how much it would cost to fix the problem than diagnosing what the problem was. This, coupled with her obvious lack of sympathy, made me doubt her diagnosis, so I had to go to another store (Chandler) to get a second opinion. I got a bad taste in my mouth (so to speak) from the experience. And that’s why I don’t go to the Biltmore store anymore.

Oddly enough, sympathy for my problem seems to be important to me. My main work computer or “production” machine (currently a Dual G5) is like a partner to me. It holds onto the projects I’m working on, it has the tools I need to get the job done as smoothly as possible. When it works right, we’re a team getting the job done. When it starts acting up, I get concerned. It’s not just a machine on the fritz. It’s a work partner feeling ill. What’s the problem? Can I fix it before it becomes critical? Is its motherboard about to go (again)? Or its hard disk? Will I lose data? Will I need to take it to the hospital (fix-it place) to get it working right again? How long will we be apart? And, of course, the selfish questions, like how long will I be unable to work?

The geniuses at the Chandler store are always sympathetic to my problem. They understand that my computer isn’t just a machine I use for e-mail and to surf the Web. They understand that its hard disk contains lots of important information — including books in progress — and the tools I need to get my work done. They understand that without my production computer, there’s very little real work I can do. And even though they don’t necessarily push any harder to complete a job for me than they do for anyone else, they make it seem as if my problem is one of the most important ones they’ll tackle that day. And they soothe me with reasonable reassurances that make it easier to face the 90-mile drive home and wait for their call.

This time around, the problem was a toasted hard disk. Personally, I believe it has something to do with my Firewire ports — it occurred while my iSight was plugged in and I was attempting to suck something off a portable Firewire hard drive. (My motherboard problem also manifested itself when working with multiple Firewire devices, including an iSight, so I’m very wary of using it these days.) They replaced the hard disk — which IS something I could have done myself if I really wanted to — and managed to get about 50% of the data off my old hard disk before it ceased to function at all. This cost me dearly, but the way I see it, I was paying for my own stupidity. If I’d had my entire Home folder backed up, recovery wouldn’t have been necessary at all and I could have saved the $150.

What hurts even more is that I’d written an article for Informit.com about backing up with Fetch before I had the problem and neglected to utilize my own instructions to protect myself.

The computer was done the next day and my husband, Mike, picked it up on his way home. It isn’t exactly on his way — he works about 15 miles north of there — but it was a lot more convenient for him than for me to make the 180-mile round trip drive. On Wednesday morning, I set about restoring the whole computer to it’s normal setup. I didn’t like the way the Apple folks had set up the machine — for some reason I was really bugged about my home folder being called maria (note the lowercase) rather than its usual mlanger (which I’ve used on all my computers for years). (Is that anal or what?) So I pulled off the recovered data, reformatted the hard disk, and spent the next two days installing software and updates. The updates were particularly painful now that I’m on the super-slow wireless Internet connection I whined about elsewhere in this blog. The 139 MB Mac OS X 10.4.8 combined updater took quite a while to suck off the Internet before I could install it.

Fortunately, I managed to pull e-mail messages, endo settings and contents, ecto contents, and some other stuff off my PowerBook. My iCal and Address book data was already set up to synchronize with .Mac, so getting all that data moved over was very easy. The only thing of real value that I lost was Chapter 6 of my Excel 2007 for Windows book, which I’d been working on for the second time. (The first revision went bad and I started from scratch. So today I look forward to starting my Chapter 6 revision for the third time. I knew it would be the book’s Chapter from Hell, but I couldn’t imagine how hellish it would be.)

By Friday, the computer was 90% back to its old self and I was working on it regularly instead of my laptop. So I was out of commission for two full weeks. I blame myself for that, too, letting the disk recovery software run as long as I did before finally bringing it to the geniuses.

5 Tips for Staying Focused

Posted on by
2

Some things that work for me.

I’ve been having trouble staying focused on my work these days. It seems that the number of distractions at my desk exceed the number of reasons I should work on my current work-in-progress, Excel 2007: Visual QuickStart Guide.

I’ve come up with a few tips that help me stay focused on a specific project or task. You may have heard some of these elsewhere; I’ve been reading a lot of about productivity tricks lately and have been linking to other articles. But this is my take on these techniques — whatever that’s worth.

  1. Organize your workspace so it has everything you need to work on the project — and just that. If you’re as likely to succumb to distraction as I am, anything handy that’s unrelated to the task at hand will pull you away from it. Ditto if you have to get up and get something that you need that’s not handy, especially if getting up takes you past the fridge, the phone, or any other distraction.
  2. List the steps you need to complete to get the job done. Think the job through before you begin so you know what has to be done. Amend the list as you work. Before starting any task that’s not on the list, ask yourself if it’s really part of the project. If so, add it to the list and do it. If not, don’t be tempted.
  3. If you don’t need an Internet connection to work on your project, turn it off. That’s as easy as turning off your AirPort card (on a Mac), unplugging your Ethernet cable, or turning off/unplugging your router. One tip I read online recently suggested using a light timer to turn off the router for a certain amount of dedicated work time each day. Personally, I like to be more flexible.
  4. Don’t check your e-mail. If you have to keep your Internet connection turned on for your work, don’t run your e-mail application. If you do and it checks e-mail periodically (as most do), you’re very likely to be distracted by an incoming e-mail message. I know I always am. Best to not to run your e-mail application at all.
  5. Don’t run applications you don’t need to get the job done. That includes (especially) Web browsers and other distracting applications. If you’re often tempted with games and are fortunate enough to have more than one computer, delete every single game you have from your work machine so you can’t be tempted to play when you should be working.

Remember, I work alone in an office, so I’m not usually distracted by other people. If you have distractions from others, be sure to check out “18 Ways to Stay Focused at Work” by Dave Cheung. His article includes some tips for keeping co-workers from ruining your productivity.

Polishing the Apple iPhone

Posted on by
Comment

Is the iPhone the answer to every problem?

From “NPR: Polishing the Apple iPhone” on The Unger Report:

Steve Jobs of Apple is known for his ability to imagine a product that has all the bells and whistles the market loves. Humorist Brian Unger imagines some features for the new Apple iPhone that Jobs overlooked.

A podcast episode that’ll make you smile.