Blogger or Writer? Not Both?

An article and podcast from a former blogger.

I listened to the podcast first. It was in my iPod after updating yesterday, among the other Slate Magazine Podcasts. Its title sent a chill down my spine, “Stop Blogging, Start Writing.”

But the interview with the author left me with the sneaking suspicion that her “last entry” was just an attempt to get some publicity. She sounded like a giggly airhead. She admitted that she had trouble “following up” with potential assignments. Hell, she claims she’d been contacted by “several” New York publishers interested in books, yet she’d managed to come away without a single contract. Not much of a professional writer, if you ask me. Any unknown who sits around waiting for a publisher to play the ball for her doesn’t deserve to succeed as a writer.

Good things may come to those who wait, but book contracts don’t.

Still, the idea of blogging taking up too much creative juice, leaving nothing for other writing, remains with me. I looked up the article that led to the podcast interview:

Why I shut down my blog” by Sarah Hepola. She seems to echo many of my sentiments, but spoils the piece with her last sentence:

Now, if I could just turn off the TV, I think I could finally get started.

Blogging and television? No wonder she doesn’t have any time to write! Or maybe that was some kind of joke? Ha-ha?

I don’t think that author will stay away from blogging for long. It’s rather addictive — at least I think so. Something interesting happens to you and you want to write it up in your blog, partially to remember it and partially to share it with others. You learn something new, something that could help others and you want to share it in your blog. You have a deep thought or a revelation of major importance and you want to shout it out in your blog pages to see if anyone else agrees or wants to argue with you about it.

But I do agree that blogging sucks something out of a person. That something isn’t lost, though. It’s just stored away for the future.

AmazonConnect

I officially become an AmazonConnect Author.

If you regularly read these blogs, you may recall my rant against Amazon.com a few months ago. I was POed because Amazon offers free “Super Saver” shipping but, when you choose it, they delay your order. In my case, they tried to delay it for two months. Then, when I complained, they sent half my order and never sent the rest. The incident convinced me to switch to BN.com for my book buying needs. Their free shipping orders are shipped promptly and in full.

Unfortunately (or in some cases, fortunately), BN.com’s Web site lacks many of the features of Amazon.com.

Unfortunately, it lacks a decent Wish list feature. On BN.com, your wish list is yours alone and can’t be shared with others. How idiotic is that? My Amazon.com Wish List, however, can be shared with a link on a Web page or by e-mail. What better way to ensure that I get what I want for Christmas or my birthday each year?

Fortunately, BN.com lacks all the marketing junk that Amazon.com is constantly throwing at shoppers. I’m talking about recommendations, member lists, “the page you made,” and “also bought” lists. Sheesh. When are those guys going to give it up already? What really irks me is how often I connect and get a recommendation for a book that directly competes with one of mine.

The other day, I logged in to look up the availability of a book I heard about on NPR. Amazon recognized me immediately from one of the cookies it had stored in my computer. And it displayed what it calls a “plog” with a series of blog posts from a woman I’d never heard of. Turns out, this woman is an author and she evidently wrote a book that Amazon.com thinks I bought. (I don’t recall buying the book; it’s about new age healing and I don’t believe in most of that stuff.) The blog entries were of a “here’s what’s new” and “here’s how you can learn more about my books” nature — marketing through and through. I found the link sequence to make them go away.

There was also a link on my page that invited me to be one of the blogging authors. I guess they matched my name with names in their book database. (Enough to recognize me as an author, but not enough to stop recommending competing books. Oh, well.) I followed a bunch of links and got myself registered as an author with my own AmazonConnect blog.

i’m not sure how this works. It seems to me that if I write a blog entry, it might appear on pages for everyone who has purchased one of my books. Now although Amazon.com lists 68 titles for me, I only claimed about 10 as mine — no sense doing virtual paperwork for out-of-print titles. So I think that if you bought one of those 10 books and connected to your Amazon.com account, you might just see a blog entry from me.

Anyone out there qualified to try this? If you bought one of my books on Amazon.com, do try logging in to see if they push some of my prose at you. Then report back here, please, and use the Comments link to let us know.

Now this means I need to contribute to yet another blog. Just when I thought that I’d combine a bunch of my sites to reduce my blogging workload, there’s another blog to write for. But don’t worry — I won’t write nearly as much or as often there as I do here. And I won’t fill it with marketing bull.

There’s enough of that on Amazon without me adding to it.

DaVinci Code Plagiarism?

What?

Okay, so we all know that I sometimes retreat into a cave where I have no knowledge of current events. But this isn’t even current. It’s been going on since February. And even I can’t stay in a cave that long.

I’m talking about the plagiarism lawsuit over The DaVinci Code.

I heard about it today and spent some time catching up on the news with some good old Google searching. It appears that the authors of The Holy Blood, The Holy Grail (HBHG), which I thought was a work of non-fiction, are suing the author of The DaVinci Code (DC), clearly a work of fiction, for “appropriating” the central theme of their book for his. The situation is summed up quite nicely in this article from the The Times of London.

I read both books. Here’s my take.

I read DC first, primarily because it was getting so much press. This was about two years ago. I found the story very interesting — in fact, it was the primary reason I kept reading. It had a lot of fascinating “facts” and puzzles. I’m a sucker for fiction based on little-known fact and this had me hooked with its wild premise — that Jesus married Mary Magdalene, who escaped to France with their child — based on a string of facts that could just make the premise true. But as for writing style, characterization, etc., Dan Brown missed the boat, at least as far as I’m concerned.

I’m not the only one who feels this way. Frank Wilson of the Pittsburgh Post-Gazette, quoted in Opus Dei, said:

In my view, the book is unexceptionally written, with minimal character development and a third-rate guidebook sense of place. It is, however, a quick and easy read, largely because most of the chapters are only a few pages long, and just about all of them end as cliffhangers.

If you don’t pay too much attention, but sort of let the book go in one eye and out the other, you’ll get to the end before you know it. [Emphasis added.]

And Peter Millar of The Times of London (again quoted in Opus Dei — they must love this stuff) said,

This is without doubt, the silliest, most inaccurate, ill-informed, stereotype- driven, cloth-eared, cardboard-cutout-populated piece of pulp fiction that I have read. And that’s saying something. [Emphasis added.]

They said it better than I could. But there was enough page turning action to get people to read it — I breezed through the first half in a day, then finished it up a few days later — and I think the premise was more than enough to get people talking about it. The result: a bestseller from a rather average piece of writing. (It wasn’t the first and it won’t be the last.)

After reading it, I remember wondering why it was a bestseller. Maybe I missed something? I read fast and that tends to lessen the reading experience. So I did double duty and I read Brown’s Angels and Demons, too. More of the same poor characterization but with better puzzles and an even less believable plot. I don’t need to read any more Dan Brown.

Anyone who thinks Dan Brown is a great writer must read an awful lot of crap. (I’m sure that statement will get me in trouble somewhere.)

Intrigued by the whole Jesus-was-married-and-the-Catholic-Church-tried-to-hide-it thing, I sought out HBHG. I found it in my local library, of all places. It was a slow read, even for me. But I slogged through it. Lots of fascinating stuff, in painstaking detail. (Too much detail for light reading, if you ask me.) It seemed to provide all the background information for DC — the well-researched facts to back up the book’s central premise.

In fact, I always assumed that Dan Brown had read HBHG — he mentions it in DC — and had written a novel based on it. After all, how could he — a novelist — have come up with all that material by himself? It would take years to dig all that up. Or a reading list that included HBHG and a few other books that covered the same general topics.

Mind you, I don’t think it’s wrong to base a work of fiction on a work of non-fiction. And that’s where I’m having a problem with the lawsuit. Is it wrong? Am I wrong to think that it’s not?

My understanding of copyright law is that you cannot copyright an idea. Has someone changed that?

As a Guardian Unlimited article points out,

The case is also likely to clarify existing copyright laws over the extent to which an author can use other people’s research.

And that’s what scares me. Suppose I read a handful of books about Abraham Lincoln in preparation for writing a novel that takes place during his presidency. Suppose one of the books says something silly — like he was gay (hmmm, why does that sound so familiar?) — and that becomes one of the underlying themes of my book. Will the author that built the Lincoln-was-gay premise be able to turn around and sue me for plagiarism?

I guess if my book became a bestseller, anything is possible.

And then there’s Lewis Perdue, the author of Daughter of God, who claims that Dan Brown plagiarized his book. I guess he’ll be suing next. Until then, he’ll keep himself busy with his own blog, The Da Vinci Crock. I haven’t read his book, but if his claims are true, it would appear that he has a stronger case than the HBHG authors. Perhaps he just doesn’t have as much money for lawyers.

The lawsuit’s court case ended today, which is probably why I finally heard about it. You can read the Reuter’s coverage of the closing day here.

I’ll be waiting to hear how the judge rules.

Nothing by Chance

I reach for a book on my shelf and am pleasantly surprised.

I had a Grand Canyon charter the other day. Although most Canyon visitors like to walk along the rim and enjoy the view, I’ve been so tired from work lately that I thought I might like to spend my wait time in a comfortable chair in a hotel lobby, reading a book. So before leaving home on Wednesday morning, I went into our little library and pulled a paperback I hadn’t read yet off the shelf. The book was Nothing by Chance by Richard Bach.

I was introduced to Bach’s writing when I was in high school. His book, Jonathan Livingston Seagull was a huge bestseller back then and all the students who liked to read read it. (Wow, is that a weird sentence construction: “…read read…”) I don’t remember the book very well and plan to read it again soon.

This book, which was published in 1969, is one of Bach’s flying books. He wrote several of them and they’re carried by most good pilot shops. I bought this copy at least two years ago from Aero Phoenix, the wholesale pilot supply shop I used to buy products for resale in the little pilot shop I had at Wickenburg Airport. I’d bought two other books by Bach on the same shopping expedition, but had chosen the wrong one to read first and hadn’t gotten any further.

The subtitle of the book, which doesn’t appear on the cover, is “A Gypsy Pilot’s Adventures in Modern America.” It pretty much sums up the nonfiction story. I’m almost halfway finished and the story so far has been about Richard and two friends as they “barnstorm” around the midwest, attracting crowds with aerobatics and parachute jumps, making money by taking people for rides in their two airplanes. The book is no longer “modern” — unless you still live in the 1960s — and the idea of $3 airplane rides takes you back to those days. It certainly takes me back to those days: my first ride in an aircraft was in the late 1960s, when I got a helicopter ride in what was probably a Bell 47. That ride, which I took with my dad, cost only $5 per person.

Bach’s writing borders on amazing. Take, for example, the very first paragraph of the book:

The river was wine beneath our wings — dark royal June Wisconsin wine. It poured deep purple from one side of the valley to the other, and back again.The highway leaped across it once, twice, twice more, a daring shuttlecock weaving a thread of hard concrete.

I read that paragraph and suddenly felt ashamed to call myself a writer.

Fortunately, the whole book is not like that. It’s a story that moves forward, with brief interludes of wonderful imagery and flashbacks to other times in the author’s past.

I can identify with the story. I often make extra money with my helicopter by bringing it to county fairs and other outdoor events. He talks about the spectators who watch but don’t step up with their money. About how dead business can be until a passenger or two climb aboard and get the whole thing started. About flying for hours with a long line of people waiting. About waiting for hours with no one wanting to fly. He talks about trying to keep count of the passengers, about their reactions to seeing familiar terrain from an unfamiliar perspective. About the responsibility of the pilot and the joy of flight through someone else’s eyes.

It’s clear that Bach loves (or is it loved?) to fly. We have that in common.

I’m glad I pulled this book off the shelf on Wednesday. But now I’m wishing I could write its sequel, as a barnstorming helicopter pilot in the 21st century.

Dana’s Last Flight

I take a passenger on his last journey.

It all started months ago. Dana had been diagnosed with a brain tumor. He called, wanting to join a flight up the Hassayampa River so he could tell me where he wanted his ashes scattered. Talk about planning ahead.

His friend Joe had gotten a custom half-hour tour for Christmas. Joe and his wife invited Dana to take the third passenger seat in the helicopter for the flight. When they arrived at the airport, I was very surprised. Dana didn’t look good. He was having trouble walking and had become bloated from the treatments he was going through. But he was alert and eager to go on the flight. He sat behind Joe in the left passenger seat. Joe snapped photos for the book he was co-authoring with Dana.

When we got near Seal Peak, Dana pointed it out. “I want to be scattered on the side closer to the Hassayampa River,” he told us. “So my ashes get washed into the river.”

I assured him I’d make sure it was done to his request. He wanted to know how much it would cost and did some math. He said he’d have the money set aside in his estate.

Oddly enough, I didn’t feel uncomfortable about it at all. I felt kind of good. I was getting final instructions — emphasis on “final” — from a customer. There would be no guessing as to whether the place we’d drop his remains was right. I knew it would be right.

Dana got a little better, then took a turn for the worse. His caregiver called me one day. She told me he talked all the time about his helicopter flight. She said she wanted to take him for another one. We talked about money. I could tell my regular prices were a bit beyond her means. But Dana was a lifelong Wickenburg resident, one of the folks who had helped shaped the town. There was a street named after his father and a flat named after his mother. The town claimed they’d be naming one of the peaks near his home after him. Surely I could contribute something to his last days.

His two caregivers brought him to the airport at the appointed time. He didn’t look good at all. His caregiver had to practically lift him into the helicopter. But he sat up tall and seemed alert, even though he didn’t talk much. His two caregivers climbed into the back seats — it costs the same to fly one passenger as three.

A while later, we were airborne, back toward Seal Peak. He wanted to be sure that I knew where to scatter him and that he’d have enough money set aside to pay for it. From there, we flew up the Hassayampa. I asked him where the old dam had been, the one that had washed away in the 1880s and killed all those Chinese workers. He pointed it out. He also pointed out the place downstream where some of the dirt from the dam had washed up. I took him southeast, past the Sheep Mountain house. They all enjoyed the views of the lake. Then west, over Santa Domingo Wash, across Grand Avenue, and around Vulture Peak. We were flying past Rancho de los Caballeros on our way to the airport when the low fuel light flickered. Time to land.

We’d been out longer than I’d planned. But it was worth it. Dana really enjoyed the flight. And his two caregivers, who probably needed the break, enjoyed it, too.

Dana passed away about a week and a half ago. One of his caregivers called to give me the news. She also dropped off one of Dana and Joe’s books at the airport for me. It was about Constellation Road and it had a few of the pictures Joe had taken during that first flight.

There was a big write-up in the paper about Dana. I didn’t see it because I don’t read the local paper.

Joe called later in the week. We made arrangements for Friday. Dana’s brother and sister would be joining him. I explained how the ash scattering worked: we’d wrap Dana’s remains in tissue paper and toss it out over the designated scattering area.

Joe, John, and Sophie came in two cars. They were surprisingly cheerful. We went into the airport’s back room to prepare Dana’s ashes in their tissue paper wrapper. I used two sheets — I didn’t want any parts of Dana slipping out during the flight.

We took a little scenic flight over town and past Dana’s house. Then we headed toward Seal Peak. I started to climb. I wanted to be at least 700 feet over the peak so the ash package would open and scatter.

My passengers pointed out places of interest along the way. They were enjoying the flight.

I circled the peak. The wind was blowing hard from the southwest. Joe saw the spot he wanted to aim for, but when he dropped the package, the wind took it toward the river. He saw a puff of dust — a puff of Dana, in fact — before the paper disappeared from view. We headed back to the airport along Constellation Road, making a short detour to try to figure out which peak the town was naming after Dana.

On the ground, Dana’s brother asked what he owed me. I knew Dana had set aside some money for the flight. I told him that it was my honor to take Dana on his last ride. I told them that the three of them should go out and have a nice lunch on Dana and me.

When they invited me to join them, I had to turn them down. Too much writing work to do. But maybe another time.