The Helicopter Job Market

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

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

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

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.

5 Ways to Make Your Blog Posts More Readable

Learn five easy tricks to help pull readers into your blog posts.

Okay, so you’ve written an article for your blog and you’re all ready to publish it online. You’re confident that the article’s content is well-written. And you’re sure it will appeal to your blog’s regular readers.

But wait! Before you put it out to be read by the world, have you done what you can to make it more readable?

By readable, I mean formatted in such a way that visitors will be drawn into its content and want to read every word. Or have you simply composed 20 paragraphs of good, solid information, formatted as big solid blocks of text?

No matter what blogging tool you use to publish your blog, you should have access to the standard array of formatting features available in HTML. In this article, I’ll explain how and why you should use them.

Break Up Long Paragraphs

What’s less attractive on a Web page than solid blocks of text? Long paragraphs of unbroken text can intimidate readers. They look unapproachable, like a college textbook. (For me, they bring to mind the textbook in my college tax accounting course, which further reminds me of two semesters of boring hell on Mondays, Wednesdays, and Fridays.)

Break up long paragraphs at logical points. This will require some writing skill, since you can’t arbitrarily chop paragraphs up — each one must still communicate a complete thought. But shorter paragraphs are a lot less intimidating than long ones — a point that applies to sentences, too (although I can’t seem to get that one into my thick skull).

And one more thing about this: be sure to use a space between paragraphs (usually with the

tag rather than the
tag, if hand coding is required). On the Web, that’s the standard way to end one paragraph and begin another. Just starting a new line isn’t going to break the paragraph at all — at least not in the eyes of the reader.

Use Headings

Headings cue the reader about the content of paragraphs that follow them. For example, my Use Headings heading here tells you that I’m going to talk about headings in this paragraph and, likely the few that follow up until the next heading. Readers can scan your article’s headings to get a better idea of what the article covers.

Of course, there are two kinds of headings. There’s the kind that actually reflects what’s in the paragraphs they head — that’s what I’m using in this article. And then there’s the kind that doesn’t quite explain what the following paragraphs are about, but are humorous or witty. Both types can work, but for serious content, I recommend the first type.

Headings can also help with search engine optimization (SEO), but not being an SEO expert, I can’t elaborate much about this. I seem to recall reading that h1 and h2 level headings are more effective for SEO than other lower levels. I use h3 because that’s how formatting is set up on my blog and I’m not terribly concerned with SEO. If SEO is very important to you, you might want to look into this claim. Of course, for headings to be effective at all in SEO, they must be coded as headings using

and tags (or other level tags as appropriate) around them. The appearance of text coded as headings will vary depending on settings in your style.css file or other style information for your blog. (And now we’re getting a little more technical than I wanted to get in this article.)

Format Lists as Lists

If any paragraph in your article includes a list of four or more items that are longer than four or more words each, for heaven’s sake, format them as a list!

There’s nothing so boring or potentially confusing as long lists within a paragraph, especially when those lists include explanations, commas, and semicolons. Why worry about proper in-paragraph list formatting when you can simply create a bulleted or numbered list that’s clear and easy to read?

Lists, like headings, are also extremely scannable, making it easy for readers to get an idea of the content they include. They draw the reader in by giving them information in bite-sized chunks. Bold formatting used at the beginning of a list item (see below) can act as a heading, letting the reader know that an explanation or more information about the item follows.

In summary, lists can do the following for you:

  • Break up long blocks of text. Long lists in a paragraph make big, fat, intimidating blocks of text. Isn’t this much nicer?
  • Make one point easy to distinguish from the next. Since you (and your readers) don’t have to worry about how list items are separated (comma or semi-colon?) you don’t have to worry about someone misunderstanding list items.
  • Take advantage of built-in formatting options. I’m not just talking about standard bullets and hanging indents here. As you can see in this list, a blog’s style.css file can include instructions for graphic bullets or other fancy formatting.
  • Give your readers important points quickly. By presenting information in an easily scannable format, your readers can see what a list is about without wasting time. If it’s what they want to learn more about, they’ll dive in and read it.

Apply Other Formatting…but Sparingly!

There are other, more basic formatting features you can apply to text. Want some basic information to stand out? Use bold formatting (as I did in the bulleted list above). Introducing a new word or phrase? Italicize it. Got a quote to share? Here’s what I say:

If it’s longer than a dozen or so words, consider putting quotations between

and

tags. This clearly identifies the text as a quote from another author. (Well, in this case, it’s still words of wisdom from me, but you can quote me if you like.)

Don’t use ALL CAPS. It’s childish and unprofessional and considered by many to be “shouting.” And don’t use underlines. On the Web, underlines indicate hyperlinks and you can confuse your readers.

And don’t use too much formatting. There comes a point when the repeated application of bold and/or italic formatting loses meaning and simply fails to do the intended job.

Insert Illustrations

I’m a firm believer in the old adage: “One picture is worth a thousand words.” Maybe that’s why I’ve been writing Visual QuickStart Guides for Peachpit Press since 1995. Those books are full of screenshots — mine average 3-4 per page — and are excellent tools for teaching readers how to perform tasks with various software.

In regular writing — such as the writing you might do for your blog — images can also help communicate information. Did you write a software how-to piece? Screenshots of the steps would be extremely helpful. Did you write about a recent vacation? Include a few photos to show the scenes you’ve written about. Does your article explain the organization of a company or one of its departments? Include an organizational chart to put things in perspective.

On the Web, images do more than just communicate information. They also add visual appeal. Think about it as you visit sites on the Web. Which pages or blog posts caught your attention more? The ones without images? Or the ones with photos or drawings?

If you don’t have illustrations for your article and you want to include some other kind of graphic element, try text in a box. This effect, which is often used in print publications, can add visual appeal almost as much as an image can.

Let’s face it: people like to look at pictures. By giving them pictures that relate to your article, you can capture their attention and reel them in to read more about what the picture shows.

A word of warning here: Don’t use photos that don’t belong to you — doing so is likely a violation of copyright law. You can probably use company logos — if your use is consistent with the company’s rules governing logo use (normally available on its Web site) and you’re writing about the company. But taking photos off another Web site or scanning them out of a print publication for use on your site could get you in a lot of trouble. It’s stealing, plain and simple, and you could get sued. Use photos, screenshots, and drawings that you’ve taken or that you’ve received permission to use. The rule of thumb here is, if you don’t know whether you have permission to use it, you probably don’t.

Conclusion

As you can see, each of these techniques is relatively easy to implement on your blog. While it isn’t necessary to use all of them in one article (as I’ve attempted to do here), you can mix and match them as you see fit to liven up the layout and appearance of your prose.

The main thing to remember is this: the more interesting you make your text appear at first glance, the more likely you are to get readers to stick around and read what you’ve written.

Oh, and by the way, just about everything in this article also applies to your non-Web writing efforts: reports, articles, white papers, and books. You just won’t need HTML code to get the job done.