Grammar Is Important

Note: Okay, so I’m recycling this one. It first appeared on May 10, 2007. In the past few days, it’s gotten a few comments. And since I’m thinking about writing — being in the middle of a book revision for my 70th book — it’s the kind of thing that I would write now –that is, if I had time to write. But I do have time to recycle, so here it is again. If you’ve already read it, why not read it again? I did and I liked it better this time around. – Maria

Some advice for people who want to make money as a writer.

I’ve been writing for a living since 1990, when I quit my day job to become a freelance writer. Since then, I’ve written 68 books and literally hundreds of articles about using computers and other topics.

One thing that amazes me is the number of people who claim they want to be writers but can’t get something as simple as grammar even close to right.

I’m Not Perfect, But I’m Okay

Okay, so here’s my disclaimer: I never claim to have perfect grammar. On the whole, my grammar is pretty good — certainly better than average — but this isn’t because I study grammar. It’s because I read a lot and always have. I believe that reading teaches good (or decent) grammar simply by example.

I use Microsoft Word with the spelling checker turned on (mostly to catch typos, but I admit my spelling skills have slipped over the years) and the grammar checker turned off. My grammar skills are better than the checker inside Word and I consistently find errors in its preprogrammed logic when it’s turned on.

My opinion: Anyone who must rely on a computerized grammar checker to get grammar right should not pursue a career as a writer.

(Allow me to digress for a moment. Back in the early 90s, when I was struggling to make my writing career work, a friend of mine was working as a temp for a company that hired out people with computer expertise. She encouraged me to check out the temp company and sign up. I went to their office in Manhattan with a copy of my first book in my briefcase. Silly me: I thought being a published author would help me get my foot in the door. They made me fill out a form that had the same exact information as my resumé — I never could figure out the bullsh*t of making a person rewrite his resumé on an application form — and then gave me a grammar test. Yes, a grammar test. They wanted to see if I could write. I guess carrying around a 450 page book with my name on the cover wasn’t enough evidence for them. So I took the test. And can you believe it? I got one of the 20 questions wrong. It was the old who’s vs. whose. To this day, I still struggle with that one. In case you’re wondering, they never called me. And I admit I’m pretty glad about that. The whole experience was completely demeaning.)

An Example of a Wannabe Writer Who Needs Help

A while back, I received a communication from a blog reader who wanted to be a writer. Here’s what she wrote:

Thanks for sharing how you make it as a writer. I have always had the dream of being a writer, but just never seem to get with the program.

This is America so I ask my self why not write. I really don”t have a style of my own yet so it will be easier for me to do things the way that publisher want them done.

I just need a topic, or an area of intrest. I heard it said that after you get a topic you will write. (Hope this is true.)

I draw your attention to the second paragraph’s first sentence. Not only does this wannabe spell myself as my self, but she’s completely screwed up punctuation in the sentence, leaving the reader to figure out what she means. The disagreement between noun (publisher) and verb (want instead of wants) could be a typo, but I can tell you right now that publishers don’t want typos.

The third paragraph (also with a typo in the word intrest which should be interest), also has a grammar problem. Can you spot it? Think about it.

Take My Advice

If you want to be a professional writer — that is, if you want to write and get paid for it — you need to understand the basic rules of grammar.

Here are three tips for improving your grammar:

  • Read. Read a lot. Read good quality writing. There’s plenty of it online, on quality publications such as newspaper Web sites, Slate.com, Salon.com, and numerous others. All of these sites have editors who check the grammar, spelling, and punctuation of the writers. Don’t read just blogs. The average blogger is not a writer and very few blogs are edited. Worse yet, many bloggers have their own “style” that shuns standard grammar and spelling.
  • Elements of StyleIf you still think you need help, read a grammar or style book. Lots of people like the Elements of Style by William Strunk Jr. and E.B. White. (I prefer the illustrated hardcover version.) But there are lots of other books out there. The Elephants of Style by Bill Walsh is lots of fun and very educational. Go to a bookstore (you know, the place you hope to find your name on the cover of a book) and check the Reference or Writing sections. You’ll find plenty of options.
  • When you finish writing something, read it out loud. Unless the language you’re writing in is not your first language, grammatical errors should jump off the page at you as you read them. Simply said: Your writing should sound good when you read it aloud. That’s not just grammar, either. It’s also the rhythm of your writing, the combination of long and short sentences. That’s something that comes with a lot of experience as a writer.

Don’t worry about developing your own personal writing style. It’ll come to you — if you don’t try to force it. Learn the basics first.

Then just write, write, write — until you get it right.

eZineArticles.com

Could be hazardous to your good name.

A few months ago, I read a blog post by some A-list pro blogger that briefly discussed eZineArticles.com as a place to publish articles and generate hits for your site. The idea was that the articles contained a byline with links and people who read them would come back to your site to read more. The result: more hits.

I dug deeply into my well of content and found a handful of articles I didn’t mind republishing. I formatted them as required and submitted them to eZineArticles.com, after setting up an account as an author. A bunch of the articles were bounced back because they read like blog posts. But I successfully argued that they did provide useful information in my somewhat conversational and bloggish writing style. All five articles were published on the eZine Articles site.

First Surprise: Anyone Can Republish!

What I didn’t realize at first was that anyone who sets up a publisher relationship with eZineArticles.com could republish my work, as long as it was republished exactly as written and included my byline, bio, and links. I discovered this when an article I wrote about flying at sunrise was picked up by a Web site with content about cruising.

After a few e-mails went back and forth between me and the site owner and eZineArticles support staff, I realized what I’d missed by not reading the fine print — I was basically granting a very broad set of rights to eZineArticles.com. But the site that had used the piece was a high quality site and I didn’t mind my recycled work appearing there. And the eZineArticles folks assured me that publishers had to meet certain requirements to use the work.

Second Surprise: Hot Sex?

But I wasn’t very happy when I traced a link to one of my Antelope Canyon photos article to a Blogger blog with the words “hot-sex” in its domain name. Although the site didn’t appear to contain any porn, I didn’t want my content — or name! — associated with it. So I wrote to eZineArticles support to complain.

Today, I found the same article used on a site with “nurse-fetish” in the domain name. Now I was pissed. I wrote again to the eZineArticles staff.

eZineArticles.com Responds

My new message crossed their response to the first one in the ether. In their response, they told me that if I didn’t want my work on a specific site, it was my responsibility to contact the owner of that site and ask him to remove it.

Ever try to contact the owner of a Blogger blog? It’s not possible if they don’t want to make it possible.

I replied that their response was completely unsatisfactory and that I would be deleting all of my articles from their site.

And then I did.

Lessons Learned

I am certainly not desperate enough to be published or to get hits by releasing my work on a site that allows distribution without prior approval by the author. Frankly, I don’t think any author should be that desperate.

eZineArticles.com obviously doesn’t give a damn about its authors if it won’t work to prevent this kind of activity with an author’s work. Any author who publishes with them deserves whatever shit he gets — including his name spread around on sites of questionable quality and purpose.

From now on, I will publish my work electronically in only three places:

  • Here, on this site, where my work is covered by a copyright notice that helps protect my work from misuse.
  • On the sites of publishers who pay me for my efforts and protect our copyrights.
  • On the sites of other bloggers who have asked me to guest author for them and will protect our copyrights.

I’m angry about this, but I know it’s my own fault. I was conned, first by the pro blogger who pushed eZineArticles.com and then by eZineArticles.com itself. I don’t understand why anyone would allow their work to be reproduced in a way that they cannot control. Could they all be as stupid as I was when I signed up?

As for the “hot-sex” and “nurse-fetish” sites, I wonder how the other female eZineArticles authors feel about their work — and their names — appearing there.

On Revisions

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.

Butterfly Out My Window

Finally captured in pixels.

For the past few days, I’ve been watching butterflies come and go in the Mexican Bird of Paradise bushes outside my office window. Today, I decided I needed to capture them with my camera.

ButterflyDigital cameras are incredible things. You can take 3 dozen photos of the same basic scene and at least one of them just has to be good.

This shot was taken with a Nikon DSLR with a 70-210 zoom lens. The tricky part was focusing — the darn butterflies wouldn’t stay still and there’s just enough breeze outside to move the flowers around. But with a quick shutter speed, several of the shots came out pretty good. I think this might be the best.

Photo Info:
Camera: Nikon D80
Shutter Speed: 1/800th
Aperture: f5.6
Focal Length: 210mm
ISO: 200

A Helicopter Ferry Flight with a Special Guest

I learn a little about the world from a pilot friend.

I flew my helicopter down to Williams Gateway airport in Chandler yesterday. I need to have some work done on it and that’s where my Robinson mechanic, Kelly, is based. It’s about a 45-minute flight from Wickenburg. Although it’s a lot more pleasant to fly in the morning this time of year, the plan was to work until 3 PM on my Leopard book, fly down there, get picked up by Mike, have dinner in an interesting restaurant, and drive back together.

Company for the Flight

Sometime earlier in the day (just as my office was really heating up with the air conditioning broken), I got the bright idea to see if Alta was home and wanted to come with me for the flight.

Alta had flown with me once before from Chandler Airport, back in the days when I was working on my commercial ticket and was leasing my little R22 back to the flight school. I’d drive down on a Friday and fly for an hour or two with my instructor, then leave my car at the airport and fly the helicopter home. On Monday, I’d fly the helicopter back to Chandler, fly with an instructor for an hour or two, and drive home. Alta accompanied me on one of my flights — I think it was a drive to Chandler/fly to Wickenburg day.

Alta is a flight engineer on 747s. She’s in her early 60s now and works for a charter operation that does mostly freight. Her schedule keeps her out of Wickenburg a lot of the time, which she doesn’t mind very much because, like me, she sees its limitations and needs more out of life. She travels frequently to China and countries that used to be part of the USSR. She occasionally sends postcards of these weird places and I post them on my refrigerator for months on end, wondering what it would be like to actually visit them myself. She’s good company because she’s not only a good listener — which everyone appreciates — but once you get her talking, she’s full of interesting stories.

But because she’s out of town so much, I was very surprised when I called her at home and she answered. I told her what I had in mind and she said she’d be happy to come along.

Delays at Home

The air conditioning guy was supposed to show up at 11:30 AM. He actually showed up at 2:30 PM. In Wickenburg, being 3 hours late is not even considered late. In fact, I considered myself lucky that he came the same day I called. I’m still waiting for the screen guys and I’ve already crossed two landscapers, a builder, a carpet guy, and two painters off my list. (If these can’t return repeated phone calls, they certainly won’t get my business.)

But what was really lucky about the whole thing is that the problem was just a blown capacitor on our 10-year-old heat pump unit. So the entire repair, with service call and diagnostics, was only $150. That compares favorably with the $1,400 we expected to pay for a new unit plus installation.

And today I’ll be comfortable in my office while I work.

Of course the late arrival of the repair guy made me late. I was supposed to stop at a neighbor’s house to try to fix her printer (don’t ask) on my way to the airport. But I didn’t get out of the house until 3:15. So I had to blow that off and expect to apologize profusely about it today. When I got to the airport, Alta was there, waiting for me. I don’t have her cell phone number — I’m not even sure if she has one — so I couldn’t call to tell her I’d be late. (When I called her house, she was already gone.)

The Flight Down

Alta accompanied me to the hanger and kept me company while I preflighted, threw my door in the back, and pulled the helicopter out to the fuel pumps. Alta used to work for me when I had the FBO at Wickenburg Airport. She was one of my best people because she understood what I was trying to do there and had the right attitude about the work. I filled her in on airport gossip as I fueled the helicopter. Then we unhitched it from the towbar, put the cart in the hangar on its charger, and walked back out to the helicopter. It was 3:45 when I finally started the engine.

It was hot. 106°F on the ramp. My door was off, but that didn’t do enough to cool us down. By the time the engine was warmed up — very quickly, I might add — we were both dripping. I made a radio call, picked up, and made a textbook departure down the taxiway parallel to runway 5 with a turnout over the golf course to the southeast

It was a typical late summer afternoon: hazy, hot, and humid. Back in New York, they call that a 3-H day. But in New York, the big H is for humid; in Arizona, it’s for hot. The humidity was only 20-30%, but with surface temperatures in the sun approaching 140°F, it really doesn’t matter how humid it is. Anyone outside will suffer.

With my door off, there was just enough air circulating in the cabin to dry the sweat on our bodies, thus keeping us cool. I’d brought along two bottles of cold water and I sucked mine down. Dehydration is a real issue in Arizona, especially in the summer.

There was enough wind and thermal activity to keep the flight from being smooth. So we bumped along at 700 feet AGL, making a beeline for Camelback Mountain. My usual route is to pass just north of Camelback and east of the Loop 101 freeway, thus threading my way between controlled airspaces so I don’t have to talk to any towers until I get to Williams Gateway.

But as I approached the Metro Center mall on I-17 I thought I’d take Alta down Central Avenue through Phoenix. That meant talking to the tower at Sky Harbor. I dialed in the ATIS, listened to the recording, and then switched to the north tower frequency.

Good radio etiquette requires you to listen before you talk. This prevents you from interrupting an exchange between the tower and another aircraft or, in a UNICOM situation, between two aircraft. I listened. For a full minute. Of silence. I was just starting to think I had the wrong frequency when a Southwest Airlines pilot called the tower. When they were done talking, I identified myself and made my request. The tower cleared me to proceed as requested. I’d go down Central Avenue, then make a left at Baseline. Along the way, I’d cross the extended centerlines for Phoenix Sky Harbor Airport, where the jets were taking off to the west, right over where I’d be flying. (You can read more about flying this route in “Phoenix Sky Harbor to Grand Canyon.”)

PhoenixAs we flew through Phoenix, Alta seemed very interested in landing opportunities. “You can land in just about any of those parks,” she pointed out.

I knew what she was thinking about. When you train to be a pilot, you’re trained to always think about where you could land in an emergency situation. Phoenix, unlike New York or other older cities, has lots of open space, including parks, vacant lots, and parking lots. There are actually more emergency landing areas in Phoenix than there are in Wickenburg — if you can imagine that.

I wondered briefly what kind of emergency landing zone you’d need to land a 747 in trouble.

All the time, of course, I was descending. I had to be at 1600 feet MSL or lower by the time I got to Thomas Road. By the time we got to the second bunch of tall buildings on Central, we were only about 100 feet off some of the rooftops. I was winding my way between them, about a block west of Central. Then another quick drop in altitude as we crossed the riverbed and I could start to climb a bit again.

I always have trouble remembering which road is Baseline, so I checked street signs as I flew. Phoenix has these very large street signs hanging from traffic signal poles, making it pretty easy to find a street’s name — even from 500 feet above it. I turned left at Baseline and we headed east. A while later, I passed out of the Phoenix surface space. I told the tower I was clear to the east and squawked VFR again.

The final challenge was landing at Williams Gateway. Although I’ve landed there at least a dozen times, I never seem able to manage my approach and landing just the way the tower wants it. They simply are not clear with instructions. To make matters worse, the taxi/ramp area is a bit complex, and doesn’t line up with the runways. So I always fly with an airport diagram handy.

Yesterday, when I called in, the tower asked me if I was familiar. Although admitting it always seems to get me in trouble, I admitted it again: “Zero Mike Lima is familiar.” Now I had to get it right or get yelled at by the tower. Again.

This time, I screwed it up again, but not as bad as usual. Check out the diagram below. The Orange line is what I did last time. Very wrong. I overflew some buildings that I wasn’t supposed to overfly. The Blue line is what I did yesterday. Closer, but not exactly right. After landing, the tower said, “Next time you come in, fly direct to that spot parallel to the runway.” So I think he means I should follow the Green line. I’ll try that next time.

Williams Gateway Airport

Fortunately, leaving is a lot easier. I just get into position between the runway and ramp on the northwest side of the airport and take off parallel to the runway.

Kelly and his assistant, Kim, came out with ground handling wheels as I shut down. I put the door on the helicopter. They insisted they didn’t need our help dragging it in, so I didn’t argue. I was glazed with sweat. When the helicopter was parked in the hangar, we discussed the work to be done, then left him. It was 5 PM.

Story Time

Mike was waiting in the main terminal, reading a magazine in air conditioned comfort. He told us we looked glazed and we went into the Ladies’ room to splash water on our faces. We then went to dinner. Our first choice, Duals, which was right near the airport, had gone out of business. (It’s a sad state of affairs when people would rather eat in some nationwide chain with the same old menu and factory-prepared food than in a nice, local place.) So we headed over to Ahwatukee and had dinner in an Italian place off I-10. I wish I could remember the name. It’s a nice little place with good food and good service at a reasonable price.

During dinner, Mike quizzed Alta about some of the places she’d flown. Although she’d told me some stories during our flight, she really opened up when questioned. She explained to us that in many places of China and former Soviet Union countries, people were poor to the point of living in ditches and starving. In China, she told me, it’s so bad that people have begun selling their children to brick factories since they can’t afford to feed them anyway. She said that the Chinese people could make do with all kinds of things we’d consider trash — for example, she said, they could make a cart out of two broken bicycle wheels. Sometimes a family of 5 would ride together on a single motorcycle. She said that many people had no knowledge of the things we take for granted.

She told us a story about landing in some former Soviet country — I can’t remember which — that had no security in the cargo area of the airport. When they parked the jet, there were young couples walking hand-in-hand along the ramp area — a cheap date looking at the big planes. She said there were a number of relatively well-dressed young women in the area, collecting planks of wood that had broken off shipping palettes. The flight mechanic told her that these people had nothing at home and were collecting the wood to make benches and other furniture. The mechanic called her down from the flight deck to meet one of these young women and Alta brought her up to the cockpit to see where she worked. Alta said the woman looked very nervous about being there, like she was afraid she’d get in trouble, so Alta cut the visit short and brought her back down to the ramp. She realized later that all of the woman’s friends and acquaintances had seen her go into the plane and that had given her a certain status among them. On their next trip through, she brought Alta a dress as a gift. Alta never got the dress — someone else apparently walked off with it — but she was amazed that this woman, who had nothing, would thank her with such a generous gift.

She also told us a few stories that illustrated the complete lack of quality control in China. She explained that the Chinese people think the point is to make something look good and polished. That’s why they put lead in toy paint — it makes the colors brighter. They sacrifice quality and safety for appearance because they simply don’t understand the importance of quality or safety. That’s not a part of their lives. “If they find a pair of shoes that they can walk in, they’re happy,” Alta explained. “It doesn’t matter if the shoes don’t fit right or fall apart in a month.”

This made me understand the whole Chinese quality problem. It isn’t because they’re trying to make cheap crap. It’s because that’s all they think they have to make. Their standards are so much lower than ours that they think they’re doing a fine job. And because the price is right and Americans have a “disposable good” mentality, we don’t mind buying the same cheap crap over and over. If it breaks, we think, we’ll just throw it away and get a new one. It’s cheap enough. We don’t see the effects on our landfills and in our own economy.

On the drive home, Alta told us about some of her more interesting experiences overseas. Being ignored by airport officials while she was trying to do her job in Dubai because she was a woman. Losing engine on takeoff in Kazakhstan when the aircraft was near max gross weight — 637,000 pounds! Overflying Baghdad, which she does quite often, and being given specially coded transponder codes. Seeing the border of Iraq and Kuwait from 30,000 feet, lit up in bright, white light. Walking down into the cargo hold to check on live cargo like horses and brahma bulls and thousands of baby chicks.

She lives in one world and works in many others. But he time as a world traveler is getting short as she grows older and the newer planes do away with the engineer position. She said it all at one point yesterday: “I’m an antique flying an antique. Does that make me a classic?”

I assured her that it did.