The Trouble with Tech Editors

Not usually the problem.

From about August 10 until just the other day, I was working on a book revision. It’s my third pass at this software manual that’s now distributed in ebook form. I’m not sure if I’m allowed to mention what it’s for, so I won’t. It doesn’t really matter, does it?

This book was unusual in that for the first time, it was the technical editors that gave me headaches. (Usually, it’s heavy-handed copyeditors.) My publisher waited until the last minute to contract me and everyone else who worked on the book and, because of that, they had trouble getting a good technical editor. They wound up with two people who apparently have nothing better to do than hang out in the support forums for the software and quite possibly hang on every word posted there. The first one worked on Chapters 2-14 before going on vacation. The other one worked on the rest of the 23-chapter book.

The problem I had centered around their apparent misunderstanding of what their job was. The first one kept commenting to tell me to add every known technique for performing each task. I’d decided early on to stick to menu commands and shortcut keys whenever possible, but she kept telling me to add this toolbar button or that hidden dialog option. It got on my nerves until we told her to stop. The other thing she did was introduce obscure problems that people in the forums have, apparently expecting the book to cover them all.

The other tech editor also drew upon his forum experience, this time expecting me to include marketing material that would clarify information about the features so forum participants would have less to complain about. The book’s a straight how-to — technically, it’s the software manual — so addressing the issues of a handful of forum whiners (the worse kind) isn’t part of the program. But what really got me mad was that this second editor was apparently unable to follow the instructions as written and kept telling me that things didn’t work. I’d have to go back and follow the instructions to see where I’d screwed up. But every single time, the instructions worked exactly as I’d written them. This was a huge time suck.

To be fair, they each did have a few comments that were actually worth acting on. I made a handful of changes that improved the book. That’s what their job was — to help me improve the book. But they didn’t seem to understand what would make the book better. All they seemed to know was what would make the book longer.

What neither understood is that I had about 15 days to revise a 600-page book. That’s not enough time to rewrite the book. All I had to do was add or change material for new or changed features. There weren’t many changes. The book, which was originally written by the software developer’s staff, had very few tech edit comments in the two previous editions I worked on. So I couldn’t figure out why these two editors kept coming up with comments that no one else had.

It’s the damn forums, I guess.

Sunrise from Wenatchee Heights

A time-lapse to remember.

For the past five weeks, I’ve been living in my RV on the side of a hill overlooking the Squilchuck Valley south of Wenatchee, WA. Every morning, I’ve watched the sun’s golden light spread out over the valley, illuminating the hillsides, mountaintops, orchards, and grassy knolls around me.

The view out the door of my RV for the past 5 weeks.

I’m leaving next week and although I think I’ll be back next year, I might not. I wanted to capture the experience to remember it.

So at 4 AM, I was outside, setting up my time-lapse camera. One shot per minute, compiled at 6 frames per second yields this 28-second video. Enjoy.

Planning the Big Move

I make plans to move my “rolling mansion” and helicopter from Wenatchee to Page, AZ.

My last cherry drying contract for the season ends on Wednesday, August 25. I need to be in Page, AZ with my trailer and helicopter by the middle of September. I’m just starting to plan for the move.

This is an exercise in logistics that I go through twice a year. Every time it’s slightly different.

The fun starts on Thursday, when my husband arrives on a late flight into Wenatchee. We’ll spend a few days in the area on a mini vacation. It’ll be the first time I’ve seen him since May 15. He goes home on Monday morning.

The move starts on Sunday, August 29 (weather permitting) with a flight over the Cascades with the helicopter to Boeing Field (BFI). With perfect weather, the flight should take less than an hour. But I’ve only had perfect weather once in the ten or so times I’ve made the flight. The last time I did it, it took about 4 hours because I had to fly all the way down to the Columbia River at Hood River to get under the clouds.

Planned Routes

Two different routes to get from Wenatchee to Seattle by helicopter. The red route includes a stop at my friend Don’s house.

Moitek Mount

My new Moitek Video Mount, pictured in my friend Erik’s helicopter.

At BFI, I’ll take possession of my new Moitek Video Mount, which I bought from the estate of a helicopter friend who passed away last year. A videographer who used the mount with my friend will be meeting with us to show us how to set it up. He’ll bring along a camera and get some footage on a flight down to Longview, where we’ll meet with the mount’s designer and maker to ask questions and get other tips. I’m hoping my friends Don and Jim, each R44 owners, will accompany us for this little trip. I’d love to get some air-to-air video for a project I’ve been working on for some time.

Back at BFI, I’ll drop off the helicopter for some maintenance. It needs its blades painted (again) and since I’m coming up on my 100-hour inspection, I figured I’d have it taken care of then. It’ll stay at the maintenance shop until I return in September to pick it up.

I’ll get back over the mountains by plane or helicopter (piloted by a friend) on Monday morning. I’ll spend the rest of the day and most of the next prepping the RV for the long drive. I’ll need to put away all loose items and clean up as well as I can.

RV Route

The RV Route

On Wednesday, September 1, I’ll hook up and roll out of here. The plan (so far) is to go to Walla Walla, where I’ll spend a few days at an RV park I know. Walla Walla has some great restaurants and wineries. It’ll be like my own little vacation on the way home.

On Saturday or Sunday, I’ll get an early start and hit the freeway for the 10-hour drive to Salt Lake City. If some friends are available to meet me, I’ll go in on Saturday; otherwise, I’ll do it on Sunday. I’m planning on parking overnight at the Draper Camping World, which should be affordable and convenient. I probably won’t even bother unhooking my truck.

On Monday morning, I head out early for Page. I hope to get there early in the afternoon and find a place to park my rig for about a week. Weather permitting, Mike will fly up to Page in his plane and pick up me and Alex the Bird to take us home. The truck and RV will remain at Page until I return with the helicopter.

On Tuesday or Friday, I’ll head up to Seattle by commercial airliner. Then, on Wednesday or Saturday, I’ll start the long flight to Page. It’ll take 8 to 10 hours, so I’m likely to do it over two days. I might have a passenger; I’ll know more this week. If I do, we’ll be doing the flight on Saturday/Sunday to Las Vegas, possibly with part of the flight along the California Coast, and I’ll be going on to Page alone. If not, I’ll do the flight on Wednesday, making the best time possible to Page by flying through Oregon, Idaho, and Utah on pretty much the same route I followed to get here before the start of the season.

In Page, I’ll set up camp — probably in the campground I lived in for two months two years ago — and offer aerial photo flights over Lake Powell. I have clients meeting with me starting on September 20, so there’s definite business for at least 5 days. On September 25, I fly the helicopter home, hopefully with a passenger (if she hasn’t forgotten). I’m not sure when I’ll retrieve the truck and RV; it depends on whether I have a training video shoot the following week in California.

So if you were wondering what I’ll be doing for the next month or so of my life, you now know.

I’ll be interesting to see how closely I can follow these plans in the weeks to come.

Why I Go On and On about the Cherries

I’m awed.

Cherries on a Tree

Cherries in their natural state.

If you follow me on Twitter, you’re probably sick of me tweeting about two things: cherries and the weather. I’ve explained, in detail, why the weather is so important to me this time of year. Let me take a moment to explain why I keep tweeting about cherries.

It’s In My Face

For the past month, cherries have been an integral part of my life. I’m living across the street from a very large cherry orchard. My helicopter is actually parked in the orchard. I drive or walk into the orchard nearly every day. I’ve also spent literally hours flying over the orchard’s trees, low-level. I feel that I have a first-hand knowledge of the orchard surpassed only by its owners, managers, and workers.

Even before I moved to my temporary home across the street, I visited the orchard. The first time was in June. Back then, the cherries were bunches of small pink dots, clustered on the branches. A few weeks later and there hadn’t been any serious change. It seemed like they’d never get ripe.

Hydrocooler in Action

The hydrocooler with its water chiller and accompanying generator in action during the peak of picking time.

Then I moved here and started to observe the activity at the orchard. Watering every morning and night. Spraying for pests many afternoons. Bringing in hundreds (if not thousands) or red wooden cherry bins. Bringing in the portable toilets and ladders for the pickers. Cleaning out the shed. Moving in heavy equipment, like the hydrocooler and its water chiller with massive diesel generator. Preparing the tractors and bin trailers and forklifts. Distributing the bins among the rows of trees.

The cherries took their own time to ripen and the growers couldn’t rush them. When the packing plant had a high demand for fruit, some picking began tentatively, pulling the scant ripe cherries from the trees. Then quiet again as they waited.

I did my part, blowing rainwater off the trees four times, protecting the vulnerable fruit from water damage.

Picking for One

Washed Cherries

Not the best photo, I know; I snapped it with my cell phone to show off how beautiful the cherries were. I hope I don’t seem too demented.

I asked for and got permission to pick cherries for my own consumption. Two or three times a week, I’d head out into the orchard and find some trees with dark red, ripe fruit. I’d fill a small colander, then head back to my trailer with my prizes. I used my RV’s small sink to wash off whatever they’d been spraying on the fruit with cold water baths and rinses. Once clean, the fruit looked beautiful. So beautiful that I couldn’t help by take photos to share on Twitter and in my blog.

I think what I like most about the cherries I pick is the way they’re so unlike store bought cherries. They haven’t been processed. Don’t misunderstand me — processing doesn’t hurt the cherries. It cleans them, probably better than I do. But it also cuts the stems to separate the bunches of cherries and sorts them by size. In my plastic cherry bin, the cherries are still bunched together in twos, threes, and fours — just the way I picked them. Some of them even have small leaves attached. And although most of the cherries I pick are quite large, I’ve also picked the small ones that never make it into stores. That somehow makes my cherries seem more natural. More real.

Even if they’re so perfect looking that they seem fake in photos.

There’s So Much To It

There’s something about being part of the farming process that really makes you appreciate your food. People see cherries in a bag at the supermarket, but do they ever think about what went into getting them there?

This orchard is on the side of a hill that is, in some places, very steep. Someone had to clear the land of scattered pine trees, sage bushes, tall grass, and big rocks. They had to plant rows of young trees and protect them from deer and other grazing animals with tall fences. They had to put in irrigation systems that would deliver fresh water, on demand, to the bases of the trees from a system of reservoirs stair-stepping down the hillside. They had to prune the trees, spray them for pests, fertilize them. They had to protect them during harsh winters and late spring frosts.

They did this for years, nurturing the trees as they began to bear fruit and grow, always adding more trees and irrigation to expand the orchard. Now, this orchard is 86 acres, but I can see the newest, youngest trees, just planted this year, on a hillside not far away. With a few years of care, they’ll be bearing fruit, too.

It isn’t always easy. The orchard’s reservoir is filled by turning a valve that brings water down from another reservoir at the top of the hill. The other day, someone left the valve open too long. The reservoir overflowed and flooded out the overflow area. Two small dams were on the verge of breaking; one of them would have released enough water to take out a road the pickers needed to get to a far orchard block. It was fortunate that a large backhoe was available nearby. The grower was able to dig out a channel to direct the water to a nearby stream. While it must have hurt to release valuable water he’d paid for, it was better than having a road rebuilt or possibly losing access to 15 acres of trees.

Picking

Picking began in earnest about two weeks ago, then stopped suddenly for five days. It started again yesterday. This grower picks for color — they’ll go through the same trees more than once to pick only the best, ripest fruit. They’re probably about halfway done; trees I picked fruit from only a week ago are now picked clean.

I’ve already documented the picking process in my “Cherries: From Tree to Truck” video. What I’ve learned is that every orchard does things a little differently. The process here is similar, but not quite the same.

Pondside Parking

Yesterday, the pickers were parked uncomfortably close to my helicopter.

It’s going on as I type this. From my office window, I can see the pickers moving ladders. I can see their cars parked out in the orchard. I can hear the refrigerated tractor trailer truck pulling up for another load of 30,000+ pounds to take away to the packing plant. The tractors pull in with full cherry bins, the water truck sprays down the roads to keep the dust down, the forklifts shuffle the cherry bins around.

It’s a good day for picking: very cool, partly cloudy. They might work until 2 PM today — a full day, considering they started at first light.

It’s an amazing thing to be part of. Can’t help it if it makes me want to talk about cherries.

What Do You Do When the RIGHT Word is a BAD Word?

Use the bad word?

I’m trying to write a blog post about a problem I’ve seen that makes the people with this problem seem….well, like assholes.

I can list a bunch of equally “bad” words here, but since I know some of my clients read this, I thought I’d keep it as close to PG rated as I could.

And that’s the problem. I want a word that isn’t one of those “bad” words. I want a word that’s perfectly acceptable in polite company.

Restrained by Niceties

The closest almost polite word I can come up with is jerk, and even that has connotations that are questionable. Besides, it’s not strong enough. These people are beyond jerks. They’re…well, what?

It’s unfortunate that certain words, on their own, should be considered so objectionable that we simply don’t utter them in polite company. George Carlin riffed on this in his famous “The Seven Words” routine. (If you have never seen this routine or haven’t seen it in a while, watch this video. It’s more than just a list of bad words. Carlin was a genius when it came to language.) The reluctance to use “bad” words just makes it difficult for people to express themselves accurately. The word I want is asshole, but I don’t think it’s right to use it because it might offend someone. So I scratch around for the right word and only come up with more of the same.

The Meaning I Want to Convey

Asshole, DefinedThe Thesaurus in my Mac, which I don’t use very often, was no help. It didn’t even include asshole (although the Dictionary did, as shown here).

When I looked up jerk, the synonyms were just as mild as jerk is. Ass was only included because it referred to an animal as well, but it also included the secondary meaning with these wimpy synonyms:

idiot, dolt, simpleton, imbecile; dimwit, halfwit, dummy, dum-dum, loon, jackass, cretin, jerk, fathead, blockhead, jughead, boob, bozo, buffoon, numbskull, numbnuts, lummox, dunce, moron, meatball, doofus, ninny, nincompoop, dipstick, lamebrain, chump, peabrain, thickhead, dumb-ass, wooden-head, pinhead, airhead, birdbrain; nitwit, twit, turkey, goofball, putz; dated tomfool, muttonhead

The word I want doesn’t mean stupid because of some kind of mental deficiency, as these words suggest. It means stupid and offensive because of a mean streak and/or complete lack of regard for other people. That’s what an asshole is, isn’t it?

How about Dick?

Phil Plait used the word dick recently in a speech he gave to a mixed crowd at a skeptics event in Las Vegas this summer. (Highly recommended folks; it’ll help you understand how to be more convincing when trying to make a point.) It might be the least offensive of the words I’ve been able to come up with. But like sucks, I have difficulty using it — partially because I’ve had friends named Dick. (Poor guys.)

What do you, dear reader, think? Is dick okay? Not quite as strong as I want, but the meaning is pretty much there.

Any suggestions? I can’t write the blog post until I have the right word and I do want to get it written. What do you think?