Tag Archives: publishing

It’s Not That Simple

Posted on by
7

A response to a reader’s request.

The other day, I got the following email message in my In Box with the subject line “Quicken 2017 for Mac”:

As I write these words your “Quicken 2002 Deluxe for Macintosh” book sits in front of me. The time has come, whether I like it or not, to update to Quicken 2017 for Mac from Quicken 2007 for Mac. Sadly, thee’s no good documentation to use. In fact, I haven’t found any good material since your 2002 book! For all I know, you’ve moved on and no longer write books such as the one published back then. That being said, I’d like to request you consider writing a new Guide similar to the one your wrote way back then. All the best to you whatever your future ventures may be.

First, I want to thank the sender for phrasing his request so politely and understanding that I might not be writing books like that one any more. A lot of the email messages I get regarding my writing work is a lot less polite and a lot more demanding, which partially explains why the Contact page on this blog seems to discourage communication from readers. (It’s actually toned down a lot more than it used to be.)

Now let me tell you a little bit about the rise and fall of tech publishing.

The “Old Days” of Tech Publishing

Dvorak's Inside Track
This is the first book I was involved in; I was a ghost writer on 4 chapters and am mentioned in the acknowledgements.

I got into the world of computer how-to book publishing way back in 1991. I’d left my last full-time job as a Financial Analyst at a Fortune 100 Corporation the year before and was trying my hand at freelance writing. Through an odd series of events, I wound up ghost writing four chapters of a book by John C. Dvorak, Bernard J. David (who I worked with directly), and others. That led to a book that Bernard and I co-authored, which led to another 80+ books that I mostly authored alone.

Back in those days, the Internet was in its infancy. Hardly anyone had a website — I didn’t have my first one until 1995 — and services like Google, which was founded in 1996 and wouldn’t become the powerhouse it is for years, didn’t exist. When people wanted to learn, they turned to books.

Software developers knew this. They provided printed manuals with their software products. Manuals for some software could be voluminous — I remember the one I had for a version of FrameMaker that had to be at least 800 pages. But despite the availability of these reference guides, users wanted something easier to read and understand. So computer how-to books were born. I happened to be at the right place at the right time to write them.

And I was very good at it. I had a knack for learning how to use software, breaking it down into simple tasks that built progressively through the book to more complex tasks, and writing it in a way that readers found helpful.

With a lot of competition, however, not many readers got to see my books and there wasn’t much money in writing them. No problem: I’ll just write more books. My publishers — especially Peachpit Press — really liked my work and my ability to meet deadlines. They kept me busy. I once signed six book contracts in a single day. One year, I wrote 10 books.

I wasn’t the only one cranking out books. Numerous publishers had tech imprints and dozens of new titles appeared every month. Bookstores — and there were a lot more of them in those days — had trouble keeping up, but they did. Publishers published these books and bookstores stocked them for one reason: they sold.

Demand only got higher as software developers stopped including lengthy manuals with their software, favoring Quick Start books instead. And then switching to digital only manuals that they might or might not include on the software CD.

Thus began the glory days of computer how-to book authors and publishers, a period that lasted from around 1995 through 2010.

Success Comes with Sales

Quicken 99 Official Guide
This was one of my first bestsellers. Revised annually until I gave it up after the 2009 edition, it was a major source of income for me.

My financial success as the author of computer how-to books didn’t come from writing a lot of books with average sales. It came from writing two particular books, revised often, that were bestsellers. My Quicken 1999: The Official Guide was one of these bestsellers.

Quicken 2002 Mac
I was very happy to be able to write about Quicken for Mac, since I was a long-time user.

The success of one book often spurs a series of books. Quicken Press (later Intuit Press), an imprint of Osborne-McGraw-Hill, soon began publishing other Quicken and QuickBooks books. That’s how I wound up authoring Quicken 2002 Deluxe for the Macintosh: The Official Guide, the book referred to in the email message above.

I was pretty happy about this. Truth is, I’m a Mac user and had been writing Windows books only because there were more Windows users so the sales potential was higher. I’d been using Quicken on my Mac for years and knew it better than the Windows version I’d been writing about since 1998.

But my Quicken Mac book didn’t take off the way we’d hoped — there were a lot fewer Quicken Mac users and Intuit still had viable competition to Quicken on the Mac OS platform. To complicate matters, Intuit didn’t revise Quicken for Mac as often as it revised Quicken for Windows. When the next version, Quicken 2007, was released, neither Intuit nor my publisher saw a sufficient market for a book about it. So I was never asked to revise my book for future editions.

Google and the Death of Tech Publishing

Meanwhile, as publishers and authors were churning out computer books as fast as we could, the Web was growing. People were writing how-to articles and publishing them on blogs, on software support websites, on user group websites, and in online magazines. Even I did this for a long while, mostly to help promote my existing titles. These articles were free and available immediately. When search engines like Google proved to be extremely effective in helping readers find the content they sought, people started thinking twice about buying computer how-to books.

After all, why go to a bookstore or go online at Amazon to find a book that may or may not answer your specific question when you could spend a few minutes searching with Google and find the answer you need? Why wait for a book you ordered online to arrive when you could find the information you needed immediately? Why depend on the voice of one author when you could access information provided by dozens or hundreds of them?

Book sales dropped off dramatically in the late 2000s. I could see it in my royalty statements; my income peaked in 2004 and 2005 and then began a steady decline. Books about software staples like Word and Excel, that I’d revise with every new version, were dropped one after another. Publishers who had once agreed to a contract for nearly every title I proposed now declined, saying they didn’t think there was a sufficient market for the book. There were fewer and fewer new software-related titles being published. Editors who’d worked on dozens of titles a year suddenly found themselves unemployed. Publishers or imprints merged or disappeared. The few brick and mortar bookstores that managed to survive the rise of Amazon reduced or even eliminated their computer book shelf space.

By 2013, all of my book titles were officially dead — not scheduled for revision. And I know I’m not the only tech author who lived and thrived through the computer book glory days to find myself without a book market for my expertise. There are lots of us out there. The ones like me who saw it coming had a safety net to fall into; others weren’t so lucky and find themselves struggling to stay relevant and earn a living writing words few seem willing to pay for.

Don’t get me wrong — I’m not saying that computer how-to books no longer exist. They do. There just aren’t many of them. And rather than appeal to the beginner to intermediate user I wrote for, they’re mostly written for a much higher level of user about far more complex topics. Or very narrow markets that are easy to sell to.

This Reader’s Request

Fast forward to today.

The very politely worded email request from a reader quoted in full above is asking me to revise my Quicken 2002 for Mac book for Quicken 2017 for Mac. If you’ve been reading carefully, you know why this is unlikely to happen.

There is not a sufficient market for such a book.

And that’s what it’s all about: being able to publish a book that will sell enough copies for the publisher to make a profit. It has nothing to do with the author; publishers really don’t care what authors make. Their contracts routinely minimize author royalties to help the book’s bottom line. That’s all that matters. They have spreadsheets that calculate breakeven and if a title can’t break even with a decent profit, they won’t publish it. Simple as that.

Would I write and self-publish a book about Quicken 2017 for Mac? Probably not. Even self-publishing such a book doesn’t mean I’ll earn enough money to make such a project worthwhile. Let’s do the math. It would take me a good 400 hours of time over two months to write the book and prepare the manuscript for publishing. Say I need to make a minimum of $25/hour. That means the project would have to net me $10,000. Even if I managed to net $5/book after fees paid to Amazon, Apple iBooks store, Nook, etc., I’d still have to sell 2,000 copies. Are there 2,000 people out there willing to buy a book about Quicken 2017 for Mac? I seriously doubt it.

And I’ll share a secret with you: I still use Quicken 2007 for Mac. I bought but decided I didn’t like the 2015 version and I haven’t even bothered to buy the 2017 version.

So if I — a loyal Quicken user since the early 1990s — haven’t bothered to upgrade, how many other people have? And how many of them want a book about it?

The answer is simple: Not enough for me or apparently anyone else to write a book about it.

This Explains It

And this pretty much explains why I don’t write books about how to use computers and software anymore. I can’t make a living doing it.

But I’m lucky: at least I’ve found something else to make a living at.

You Can’t Go Back

Posted on by
13

A note in response to a bulk email from an old colleague.

It may be hard for some blog readers to believe, but for a while in the late 1990s and early 2000s, I was “famous.”

My fame was limited to a group of people who bought my books and read my articles about using computers. I started writing in 1991 — as a ghostwriter for a John Dvorak book — and was soon writing my own titles. I learned early on that if you couldn’t write a bestseller, you had to write a lot of books. So I did. And then, in the late 1990s, two of my books became best sellers. Subsequent editions of the same book continued to be best sellers. For a while, I was making a very good living as a writer. At the computer shows where I was a regular speaker, people actually asked for my autograph.

I’m not an idiot. I knew that my good fortune could not last forever. So as I continued to write, turning out book after book and becoming well known in my field, I invested my money in my retirement, assets that could help extend (or at least securely bank) my wealth, and something that I thought would be a great hobby: flying helicopters. I learned to fly, I got hooked on it, and I bought helicopter. I started my helicopter charter business in 2001 — it was easy to fit flights in with my flexible schedule as a writer — and bought a larger helicopter in 2005. Building the business was such a struggle that I honestly didn’t think I would succeed. But fortunately, I did.

Mountain Lion VQS
My most recent book was published back in 2012. I don’t call it my “last book” because I expect to write more. They likely won’t be about computers, though.

And it was a good thing, because around 2008, my income from writing began declining. By 2010, that income began going into freefall. Most of my existing titles were not revised for new versions of software. Book contracts for new titles were difficult to get and, when they were published, simply didn’t sell well.

Around the same time, my income from flying started to climb. Not only did it cover all the costs of owning a helicopter — and I can assure you those costs are quite high — but it began covering my modest cost of living. By 2012, when I wrote my last computer book, I was doing almost as well as a helicopter charter business owner as I’d done 10 years before as a writer. And things continued to get better.

I was one of the lucky ones. Most of my peers in the world of computer how-to publishing hadn’t prepared themselves for the changes in our market. (In their defense, I admit that it came about quite quickly.) Many of these people are now struggling to make a living writing about computers. But the writing is on the wall in big, neon-colored letters as publishers continue to downsize and more and more of my former editors are finding themselves unemployed. Freelance writers like me, once valued for their skill, professionalism, and know-how, are a dime a dozen, easily replaced by those willing to write for next to nothing or even free. Books and magazine articles are replaced by Internet content of variable quality available 24/7 with a simple Google search.

So imagine my surprise today when one of my former colleagues from the old days sent me — and likely countless others — a bulk email message announcing a newsletter, website, and book about the same old stuff we wrote about in the heydays of computer book publishing. To me, his plea came across as the last gasp of a man who doesn’t realize he’s about to drown in the flood of free, competing information that has been growing exponentially since Internet became a household word.

I admit that I was a bit offended by being included on his bulk email list simply because he had my email address in his contacts database. But more than that, I was sad that he had sunk so low to try to scrape up interest in his work by using such an approach. Hadn’t he seen the light? Read the writing on the wall? Didn’t he understand that we have to change or die?

So after unsubscribing from his bulk mail list, I sent him the following note. And no, his name is not “Joe.”

The world’s a different place now, Joe.

After writing 85 books and countless articles about using computers, I haven’t written anything new about computers since 2012. I’m fortunate in that my third career took off just before that. Others in our formerly enviable position weren’t so lucky.

Not enough people need us as a source of computer information anymore. All the information they could ever want or need is available immediately and for free with a Google search. There are few novices around these days and only the geekiest are still interested in “tips.” Hell, even I don’t care anymore. I haven’t bought a new computer since 2011 and haven’t even bothered updating any of my computers to the latest version of Mac OS. My computer has become a tool to get work done — as it is for most people — a tool I don’t even turn on most days.

Anyway, I hope you’re managing to make things work for yourself in this new age. I’m surprised you think a newsletter will help. Best of luck with it.

And if you ever find yourself in Washington state, I hope you’ll stop by for a visit and a helicopter ride. I can’t begin to tell you how glad I am that I invested in my third career while I was at the height of my second.

Maria

Is it still possible to make a living writing about computers? For some of us, yes. But we’ll never be able to achieve the same level of fame and fortune we once achieved. Those days are over.

Just Say No to Writing for Free

Posted on by
6

Don’t be part of the problem.

Yesterday, an editor of an aviation publication contacted me about writing for the organization’s blog. He’d found my blog through a link from another blog. He’s interested in increasing the amount of new content on his blog and wants to do that by signing up other writers. He already has a flight school operator signed up. One new post a month from each of four writers would get him the one post a week he wants for the blog. Makes sense.

From his email to me:

It’s quite difficult to find working helicopter pilots who can write, as I’m sure you can imagine. But you definitely seem to have the knowledge and interest. Would you consider doing some additional writing for [organization]?

At first, I was thrilled. I’ve been wanting to do some more aviation writing and the publication is well-respected. But then I began wondering whether this would be a paying gig or if I’d be expected to write for free. I worded my response carefully:

I definitely WOULD be interested in joining you folks. I’m an active helicopter pilot with a single pilot Part 135 operation now based in North Central Washington. And you probably already know that I also make a portion of my living as a writer.

Please do tell me more. If you’d like to chat, give me a call.

If you read what I wrote between the lines, the phrase “I also make a portion of my living as a writer” was meant to tell him that I’m usually paid to write.

His response came an hour later:

Thanks Maria. I should tell you up front that our budget for the blog is nil. So as much as it pains me to say it, I wouldn’t be able to pay you for the work. That said, there is always potential for additional opportunities.

I have to give him credit for not telling me that I’d be compensated with the “exposure” I’d get for writing for them. That really told me that he understood the situation — any editor that offers you “exposure” as compensation is either stupid or a manipulative bastard. You can’t pay the rent or buy groceries with exposure and the only thing it really exposes you to is additional editors looking for writers who will write for free.

As you might imagine, I put it out on Facebook to get feedback from friends, many of whom are freelancers. I was careful not to identify the organization. After all, does it really matter?

Post by Maria Langer.

My post got lots of comments that are really worth reading. As my Facebook friend Carla said:

Comment from Carla

But this editor didn’t suggest such a thing. And I respect him for that.

The “additional opportunities” line, however, was obviously a lure — whether it was real or just a fabrication I’ll likely never know.

My response was frank:

We can still chat about the blog posts. I am willing to help out if it leads to other paying work. But if the additional opportunities never materialize, I probably won’t be motivated to continue writing without compensation.

Unlike the flight instructor you’re working with, I don’t have a flight school that might benefit with my name or company name getting out. My blog is already very well read by helicopter pilots — for good or for bad — and if I’m going to write for free, I’d rather write for my own blog.

I didn’t get a response.

The comments kept coming in on Facebook. All the publishing professionals and freelancers understood the situation perfectly. One of the commenters, a friend of Carla’s as a matter of fact, had this to say:

Comment from David

And that really hit home hard. The reason I couldn’t make a good living as a writer anymore was because too many people were writing for free. Publishers didn’t care much about quality when they could get free content. All they really want are hits and if something is interesting enough to attract the hits, they’re satisfied. Who cares about how it’s written? This is what’s killing the publishing industry — and giving those of us who actually enjoy reading well-written content a lot less to read.

I chewed on the comments overnight and when I woke up I knew I needed to send a new response. Here’s what I sent:

I’ve given this some more thought. I’ve decided that it would not be in my best interest, nor in the best interest of professional writers anywhere, to write for a commercial publication without compensation. Professional writers are paid for their work. Amateurs are not. I am not an amateur.

Maybe you don’t realize that I’ve written more than 80 books and hundreds of articles since 1990. Maybe you don’t realize that the money I earned as a writer enabled me to learn how to fly a helicopter and eventually buy my own. Maybe you don’t realize that my writing income kept my helicopter business afloat for its first eight years.

So not only did I earn a living as a writer, but I earned a very good living.

Sadly, those days are over. It’s now very difficult for freelance writers to find decent paying outlets for their work. I’m fortunate that my helicopter business became profitable when it did.

The way I see it, the reason [organization] is able to ask people to write for them without compensation is because too many people say yes. That’s the problem. That’s what’s bringing down publishing and the overall quality of what appears on the Web. Publishers settle for whatever they can get for free.

You say that it pains you to say that you can’t offer compensation. As a writing professional, I can understand that pain. But what I can’t understand is why someone in your position doesn’t push back and argue in favor of the writers. What’s a few hundred dollars a month to [organization]? You realize that’s all it would take. It’s the principle more than anything else.

I love to write; that’s why I have a blog. But I need to limit my uncompensated writing to my own blog — not one used to support an organization that generates revenue off the work of uncompensated writers.

I don’t want to be part of the problem.

Say No to No PayI emailed it this morning. I suspect the editor I sent it to will understand completely. But I don’t expect to be offered any money or any opportunities to write for them in the future.

Did I burn a bridge? Perhaps. But is it a bridge I really wanted to cross? I doubt it.

Are you a writer who can create quality content? If so, don’t sell yourself short. Demand compensation for your work. Don’t be part of the problem.

Postscript

Just moments after clicking the Publish button for this post, I got a response to my last email (quoted above). I was offered a reasonable amount of money for my work. I’m just hoping this blog post didn’t piss off the editor enough to make him retract his offer. (I really do respect the guy, especially now.) Yet I won’t delete this blog post because the message remains the same: professional writers should not write for free. If I lose this opportunity for making this statement and using my situation as an example, so be it.

It really is the principle of the matter more than anything else.

One more thing…

Another Facebook friend reminded me that I’d embedded a rant by Harlan Ellison in my blog years ago. Mr. Ellison says it a lot better than I could.

A New Year, A New Book

Posted on by
4

A new project to get my year off to a good start.

2013 was the first year since 1991 that I did not publish a new book.

There are several of reasons for this, none of which I want to get into here. That would make interesting fodder for a future blog post. Don’t worry; I won’t leave you hanging for long.

But it isn’t as if I haven’t been writing — I have been. In addition to this blog, which I’ve tended to quite faithfully since I started it in October 2003, I’ve been working on another book project since late 2012, when I found myself with an outrageous personal story to tell. Unfortunately, I’ve had to put that project aside; I hope to finish it when I know the ending.

Papillon HelicopterToday, however, I started work on the book I’ve been thinking about for the past month or so. Tentatively titled Flying the Canyon: My Season as a Grand Canyon Helicopter Tour Pilot, this book will share my experiences from one of the most interesting summers of my life.

Here, I’ll let the book’s draft introduction tell you more:

In the summer of 2004, I realized one of my dreams: I became a helicopter tour pilot at the Grand Canyon.

I was 42 when I got the job and I worked with a bunch of young people — mostly men — some of whom were young enough to be my kids. I met the challenges of working in a sometimes difficult but usually breathtakingly beautiful flying environment, dealing with the personalities of co-workers and management, and trying to please passengers from all over the world. The work was rewarding, frustrating, and enlightening. The flying experience was something I think every helicopter pilot should have.

I also had a very odd experience on one of my flights — an experience that would leave the lingering scar of PTSD on me for many years to come.

I thoroughly enjoyed the work, but by the end of the summer, the novelty had worn off. Friction inside the company made the job less pleasant than it had been. I realized that I was a square peg in a round hole. My real work as a freelance writer was being neglected and my editors were beginning to lose their patience. I was sad to leave, but it was time.

This book is the story of my season at the Grand Canyon. It begins before the beginning by sharing the stories of when I decided I wanted to learn how to fly and the things that I did to gain the skills I’d need to be a tour pilot. It then goes on to tell about my experiences as a pilot at the Canyon — including the unusual occurrence on June 10, 2004 — and my direct interactions with fellow pilots, management, and passengers. Finally, it shares how my feelings about being a Canyon tour pilot changed as the summer came to a close and the events that affected my decision to leave.

Because I’d blogged many of my experiences soon after they happened, much of what I share in these pages is rich with details. But rather than just restate my blog posts, I’ve filled in the gaps between them with the behind-the-scenes stories that I couldn’t make public at the time.

Ever wonder what it’s like to be a helicopter tour pilot at the Grand Canyon? Here’s what it was like for me.

As I write, I’ll be pulling a lot of my blog posts about those days offline, probably for good. In a way, my blog has acted as a temporary archive for these stories. Once the book is complete and published, the book will be the permanent archive. I hope to do this with much of the contents of my blog.

Captain MariaToday, I churned out over 4,000 words, completing the introduction (which I just shared here), a Prologue, and Chapter 1, which briefly covers my experiences learning to fly and getting my commercial pilot rating. My goal is to have the entire book finished by month-end — a goal I know I can reach if I can stay focused on my work. (With little else do do this winter, it shouldn’t be much of a problem to find time!)

I’ve toyed with the idea of shopping it around to a mainstream publishing house but will likely self-publish under the Flying M Productions “Real-Life Flying” imprint. The book will be available in print and as an ebook in Kindle, Nook, and iBooks formats. I had quite a bit of success with one of my three self-publishing projects back in 2012, so I’m pretty confident I’ll meet or beat that success with this book.

Of course, since I need to work on the book each morning, that might cut into my blogging time. So expect to see fewer posts here over the next month or so as I write, edit, lay out, and publish this book. More information on where to buy it will be available before month-end.

Comments? You know where to put them!

Twitter and Writing

Posted on by
Comment

Some thoughts on a New Yorker essay.

Twitter LogoI read an interesting essay on the New Yorker magazine’s website yesterday: “The Ongoing Story: Twitter and Writing.” It was one of those pieces that, as you read it, you realize that you and the author are sharing the same thoughts about something that you thought you were alone in thinking. As I read through the piece, I found myself wanting to highlight different passages of it — the parts of it where the author put into words what I’d been thinking or feeling for a long time.

So I figured I’d blog a little about it to store those thoughts here.

For example, the author of the piece, Thomas Beller, writes:

Most great writers could, if they wanted to, be very good at Twitter, because it is a medium of words and also of form. Its built-in limitation corresponds to the sense of rhythm and proportion that writers apply to each line.

And that’s the challenge of Twitter. Sharing a complete thought in 140 characters. I wrote about that back in October 2010 (was it really that long ago?) in my blog post titled “How Twitter Can Help You Become a More Concise Writer.” After all, anyone can write a string of tweets to tell a story. But how many people can convey that story in just 140 characters? How many people can be interesting, funny, provocative, witty, sarcastic, ironic, or insightful?

Yes, it’s true: I do tweet photos of some of my meals. (Don’t we all?) But occasionally I get more serious. Occasionally I dig deeper and come up with something witty or profound, something that other people find worthy of retweeting or, better yet, favoriting.

(Ever wonder how the word favorite became a verb? I did, too. Then I asked all-knowing Google and it pointed me to this article that explains it. It shouldn’t surprise you that Twitter is involved. But once again, I digress.)

And sometimes — just sometimes — I can paint a visual picture with those 140 characters that’s as clear as a glacial stream on a spring day.

Two more passages touch upon why and how I use Twitter:

Does a piece of writing that is never seen by anyone other than its author even exist? Does a thought need to be shared to exist? What happens to the stray thought that drifts into view, is pondered, and then drifts away? Perhaps you jot it down in a note before it vanishes, so that you can mull it over in the future. It’s like a seed that, when you return to it, may have grown into something visible. Or perhaps you put it in a tweet, making the note public. But does the fact that it is public diminish the chances that it will grow into something sturdy and lasting? Does articulating a thought in public freeze it in place somehow, making it not part of a thought process but rather a tiny little finished sculpture? Is tweeting the same as publishing?

And:

I had always thought of Twitter as being a good place to work out ideas: a place to mull things over in public, and a way of documenting a thought to make it more likely that I would remember it. But is it like a conversation or is it “talking it out?” Is it a note to oneself that everyone can see, or is it, like iPhone photos, an attempt to offload the responsibilities of memory onto an apparatus that feels like an extension of ourselves because it is always in our hands? I sometimes wonder if I might ever be accused of stealing my own idea.

And that’s how I use Twitter: as a sort of running list of my thoughts and the things going on in my life. (That might explain why I’ve tweeted more than 44,000 times since I joined Twitter back in 2007. I think a lot and keep pretty busy.) It’s easy to whip out my phone or iPad and tweet something that’s on my mind — or to save a picture of what’s in front of me in a place where it’ll be forever (or at least a long time). It is an offloading of information so I don’t have to remember things.

Mr Beller wonders whether articulating a thought in public freezes it in place somehow. It does. It freezes it in the Twitter archive, which I can download for my account and search at any time. (How do you think it was so easy for me to come up with the tweets you see here? Imagine that archive in the hands of a paranoid and delusional stalker!) That makes it possible for me to go back in time, to see what I was thinking and doing on a specific date since my first tweet in March 2007.

I can’t think of any easier way to make life notes. Stray thoughts can be captured before they drift away, to be pondered at my leisure. And sometimes — just sometimes — they become the seeds for blog posts or conversations with friends.

Twitter was introduced as a “microblogging” service and that’s exactly how I use it. I assume other writers do the same.

But is tweeting the same as publishing? I don’t think so. It’s more like standing on a soapbox in a crowded park, making random remarks. Some folks who know you’re there and find you interesting might be there to listen. But otherwise, your words go mostly unheard. You can argue that the same can be said for publishing, but publishing seems to be a more legitimate form of communication. Or maybe that’s just old-fashioned thinking on my part.

Managing the anxiety of composition is an essential part of writing. One must master the process of shepherding the private into public. There are bound to be false starts, excursions that turn out to be dead ends. But these ephemera—notes, journals, drafts—are all composed in a kind of psychic antechamber whose main feature is a sense of aloneness. They are the literary equivalent of muttering to yourself in a state of melancholy, or of dancing in front of the mirror with music blasting when you are alone in your room. Both of these are best done when no one is home.

I’ve never found it difficult to write; there is no anxiety for me. That’s not to say that I don’t have false starts and wander down to dead ends. Or, more often than I’d like to admit, write crap.

There is an aloneness to all writing, including Twitter. And yes, tweets are like talking to yourself, but with the very real possibility that (in my case) 1600+ people are listening and may respond. No one is home here except me — I’ve been alone for a long time, even when I supposedly wasn’t.

Almost everybody who is a writer these days gets, at some point, a lecture on the necessity of being “on” Twitter and Facebook. It’s a tool of selling and career building. It is, for writers of all ages and stages, not so much required reading as required writing.

I also got this lecture from one of my publishers. I didn’t need to be sold on Twitter — I took to that like a bird takes to the sky. It was Facebook that I avoided for as long as I could. So long, in fact, that I lost a contract because I wasn’t involved enough in social media. Imagine that! An early adopter of Twitter with tens of thousands of tweets not being involved enough in social media.

Twitter gives writers the ability to put ourselves out there for the world to see. Does it help my writing career? Perhaps — to a point. It certainly helps attract blog readers and give me a steady stream of intelligent people to communicate with.

After five years and more than 44,000 tweets, I know one thing for certain: Twitter has become a part of my writing life.