How Twitter Can Help You Become a More Concise Writer

140 characters or less.

One of my biggest problems as a writer is that I tend to be overly wordy. If a story can be told in 500 words, I’ll take 1000. If a how-to piece for a magazine article needs to be 1500, I’ll write 2200.

A Real Writer's KeyboardI was lucky. When I first got started as a writer, only the magazine publishers cared about word count. I’d spend a day writing a piece and then spend half the following day cutting it down to the necessary size. I still wound up submitting 10% to 20% more words than they wanted. The book publishers didn’t seem to care how many words I wrote.

Times change. When my primary book publisher started restricting page count, I knew I had a problem. It bugged me, mostly because they were willing to cut out entire chapters of a book revision just to keep the page count under some magic number spit out by a spreadsheet. Content didn’t seem to matter as much as maximizing that bottom line. The tail had begun to wag the dog.

Most of my magazine work, on the other hand, went digital. Since there is no paper and a page can be any length, they don’t care how many words I submit for a piece. Of course, payment by the word went away, too. Instead, I’m paid by the article. As long as what I submit is complete, they’re happy.

The Ultimate Limitation

Of course, my history with publishing isn’t the point. The point is, a writer needs to be able to deliver a message in the desired word count.

Twitter logoAnd that’s where Twitter comes in. With only 140 characters, it’s often tough to communicate a complex message. While many people resort to cryptic txt world abbreviations, I prefer not to. Instead, I prefer whole words and even whole sentences.

Still other people will use several consecutive tweets to tell a story. This is generally not a good idea — more than two Tweets in a row that tell a long story is generally considered bad Twitter etiquette. Besides, where’s the challenge in that?

A better idea — one that offers good practice for a writer — is to embrace the 140-character limitation. Deliver complete, grammatically correct — or nearly grammatically correct, as I’ll discuss in a moment — thoughts as whole sentences.

And this is what I attempt to do on Twitter.

Tighten It Up

Here’s how I embrace Twitter’s limitation and use it as a tool to practice tightening up my prose:

  1. In Twitter client* software — compose the tweet to say what you need to say.
  2. Check the character count. If you’re under, tweet it as is. You’re done. Skip the remaining steps.
  3. If you’re over the character count, start paring down the text. Here are the things I do in the order I usually do them:
    • Reread the tweet. Do you really need to say all of that?
    • Look at the long words. Can any be replaced with shorter words that mean nearly the same thing?
    • Kill the adverbs. This is basic writing advice that has nothing to do with Twitter.
    • Look at the adjectives. Do you really need them?
    • Drop periods after obvious abbreviations, such as Mr or Dr.
    • Kill the articles. This is where grammar begins to suffer. I have a personal rule: if I kill one article in a tweet, I kill them all, just for consistency.
  4. As soon as the character count gets below 140 characters, re-read the tweet. If it’s what you want to say, tweet it. You’re done. Skip the remaining step.
  5. If your tweet doesn’t relay your message, start over from scratch.

This exercise can be fun if you go at it the right way. Although it might seem tough the first few times you do it, it does get easier and easier. I’ve gotten to the point where I sometimes cut so much out that I can add another short sentence. Not bad.

Are you a writer or just a tweeter? If you’re a writer, rise to the 140-character challenge of Twitter without leaning on txt abbreviation crutches.

*This is nearly impossible to do on a cell phone using txting, so don’t even try.

Photo Flying, Job Shuffling, Helicopter Rides, Travel, and More

Yes, I’m still alive and kicking.

In case regular readers are wondering whether I’ve fallen off the face of the earth, the answer is no, I haven’t.

My life has been non-stop craziness since the third week in September and I’ve simply been too busy to blog. That’s not to say I don’t have anything to blog about — I do! I just can’t find a 2-hour block of time to get some good content out of my head and into this blog. This status report will have to do for now.

Aerial Photo Flights at Lake Powell

The thing that started all this craziness was the aerial photo gig I had at Lake Powell. I was there for two weeks, but the last five days were the busiest. I did 14 individual aerial photo flights, each lasting between one and two hours.

I didn’t think it could ever happen, but by the end of the third day, I was actually getting tired of flying over that beautiful lake. It wasn’t until the last two photo shoots that I started really enjoying it again. I flew with a local photographer, Gary Ladd, who directed me to show him the lake and surrounding area in ways I’d never seen it. He brought the magic back. You can see some photos taken during the two flights by Rebecca Wilks, my client for those flights, at Skyline Images. I’m hoping Rebecca lets me share some of her work on the Flying M Air Web site.

That whole gig ended with a 2.2 hour flight from Lake Powell to Deer Valley. The first half of the flight was very pleasant, including the stop for breakfast at Marble Canyon Lodge. But once we got down off the Colorado Plateau southwest of Sedona, the heat and turbulence made the flight very unpleasant. My passenger, Rebecca, was likely on the verge of being ill for some of that time; I was certainly not feeling very good either. Landing at DVT was my return home after being away since May 15, ending four whole months on the road.

Two New Jobs

Back in July and August, when I had no writing work lined up, I started putting irons on the fire. The economy might be scary for people with jobs, but it’s terrifying for freelancers when there’s nothing on the calendar. I started discussions with two different publishers, feeling I had about a 50-50 chance of getting either job.

The good news: I got them both.

The bad news: They had the same deadline.

I worked my butt off for my first full week home, trying hard to deliver content for both of them. I realized that they’d either think I was lazy or incompetent. This was not a good thing, since one of the contracts was a brand new relationship with a publisher I hope to do more work for.

I confessed to both of my editors. I was surprised — and very happy — about how understanding they were.

Now I’m at Lynda.com‘s offices in Ventura, finishing up one of those projects. On Sunday, when I return, I’ll be back at my desk, cranking out new chapters for the other project, a brand new book. I expect to be working on it daily for the next three weeks.

Helicopter Rides

I do helicopter rides every year at the Congress Days event in Congress, AZ. It’s a very small event, but it gathers quite a local crowd. I make the rides cheap enough for anyone to afford them. This year, they were $25 per person, down from $30 per person last year.

This year, the rides gig fell on October 2, which was this past Saturday. Despite my crazy busy schedule, I showed up as planned and did a bunch of rides in 95°F weather. This particular event is extremely blog-worthy due to the challenging flying conditions and I definitely will be blogging about it when I get some time. I just need to assemble some more visual aids. It’s a good lesson in high density altitude flying.

Phoenix to Santa Barbara by Way of Bakersfield

My flight to Santa Barbara (to go to Ventura this week) was a bit of an adventure. The marine layer was in at midday and the glide slope at Santa Barbara was broken. On the attempted landing, the pilot was able to get down to 500 feet (the decision height) and not see the runway. I got a glimpse of the ground through the clouds before he hit the throttles and we ascended back through the clouds.

There was no second try. He flew us to Bakersfield where we were let off the plane in a terminal with a closed Subway restaurant. When the United Airlines flight to Santa Barbara also landed there, they hired a bus to take us to Santa Barbara.

I hate buses.

When a fellow passenger rented a mini-van for a one-way drive to Santa Barbara, I was one of five other people who joined her. The $130 rental plus $20 fuel purchase came out to $25/person and I’m certain that we beat the bus by at least two hours.

So instead of arriving at my hotel by 2 PM, I rolled up after 7 PM after an adventure with five strangers.

That’s worth a blog post on its own, but I’m allowing the memory to fade and don’t want to bring it back by writing about it.

Ventura and Beyond

So here I am in my hotel in Oxnard, CA, right near the border of Ventura. It’s 6:40 AM. At 7:30 AM, I’ll be in a soundproof booth, recording my words of wisdom and mouse clicks for another new course. I’m not sure if I can talk about it yet, but you’ll hear about it soon enough. I’m happy to be here, despite the clouds and rain.

Once I get home, I’ll get back on my regular schedule of blogging. I need to blog. If I don’t write here at least four or five times a week, I get a little crazy. So just have some patience and I’ll do the best I can.

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.

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?

Guest Blogger FAIL

Another oddity from my inbox.

Here’s today’s message, with the subject “We would like to write an article for your site,” edited to remove identifying information:

Hey there,

We have been reading the articles on your website and are very impressed with the quality of your information.

We have a team of copywriters who specialize in writing articles on various topics and would like to write an original article for you to use on your website – this article will not be used anywhere else on the Internet.

In exchange all we ask is that we can have one or two links within the body of the article back to one of our sites. You can view a sample of the quality of our articles at [redacted].

If you are interested in having us write an article for your website please just let me know and we would be more than happy to have one written for you within two weeks.

Kind regards,
[redacted]

If they’re so impressed with the quality of my information, what makes them think I need a post written by someone else? Isn’t it clear that I can write my own blog posts?

And if it’s my personal blog, what makes them think I’d welcome posts from others? Did they find any posts by others on my blog?

And yes, I do realize that they likely never even looked at my blog. That this is just a form of spam that’s likely to sent out to every blogger they can find contact info for.

The question I take away from this is: Are bloggers so desperate for content that they’ll let strangers do guest posts in exchange for a couple of links?

Needless to say, I’m not interested so I don’t think a response is necessary. No need to put my e-mail address in their spam list. (They had to use a contact form to contact me.)

In a way, they did write a blog post for me. This one.