Some Thoughts on Religion

And a few books to back up those thoughts.

In trying [desperately] to catch up with the RSS feeds I follow, I stumbled across a three-part series of excerpts from Christopher HItchens’ new book, God is not Great.

Lately, religion has been on my mind more than ever before. Our country is being led by elected and appointed officials that repeatedly claim that their faith in God is what guides their decisions. And we’ve been sucked into a war where religion is the motive or justification for extremists to kill themselves and others.

I’ve never been a religious person. I’ve always believed that doing the right thing whenever possible is far more important than praying or going to church or skipping meat on Fridays during Lent. I’ve always been satisfied to let others believe what they want — as long as they don’t try to make me believe.

But things are different these days. Religion is causing deaths. Deaths of innocent people. Deaths of patriotic young men and women who go to Iraq with the misguided belief that they are protecting America. And it hurts me — a thinking person — to see so many lives lost or ruined every day in the name of religion. In the name of God.

Am I the only person seeing it this way?

Religious Literacy

Religious LiteracyI’m currently reading Religious Literacy by Stephen Prothero. The book is really two books in one. The first part of the book explains how important religion has been throughout the history of the United States. With the country’s Protestant background, religion was taught not only at home, but in public schools. As time passed and immigrants arrived with other religions, less religion was taught in school. Supreme court rulings that stopped school prayer pretty much put an end to religion in school. As a result, Americans have what Prothero refers to as a religious illiteracy.

It’s interesting to note here that Prothero makes a very good distinction between teaching religion and teaching about religion in school. While he apparently agrees that school should not be used to preach religious theories or convert students to any one set of beliefs, he believes that a curriculum that covers the basics of all major religions would be beneficial. He believes that only through knowledge of what these religions involve — beliefs, rituals, histories — can an educated person discuss and make informed decisions about what’s going on in today’s world. I couldn’t agree more — which is why I bought the book. The President may not understand (or care about) the difference between Sunni and Shi’a Muslims, but I do.

The second part of the book is a glossary of the world’s religions. Important terms are clearly defined, giving the reader a good base of knowledge. I think of it as World Religions 101. And although Prothero is quick to say that the information in Chapter 6 of his book is not all inclusive, I believe it’s a very good start for anyone interested in learning about the beliefs and histories of other faiths.

In any case, I highly recommend the book. Although the first part is a bit dry and repetitive, the second part is sure to fill a lot of holes in your knowledge of world religions. Best of all, Protheros makes no judgments at all, so his book will appeal to believers and non-believers alike.

What I Believe

As I mentioned earlier in this entry — forgive me; I still have a terrible cold and am having trouble thinking linearly with a headache and hacking cough — for the past year or so, I’ve been thinking a lot about religion. And I’ve recently concluded that I’m probably an athiest.

I say probably, because I’ve always been agnostic, even as a youngster. The conscious conclusion that I’m a non-believer was not easy to make. But looking back on the decision-making process now, I can’t understand why. It makes more sense to me that there isn’t a God than that there might be.

Before I go any further, please spare me the irate comments about my beliefs. If you think all atheists will rot in hell, fine. You don’t need to clutter up the comments for this post or send me nasty feedback to warn me. For obvious reasons, I don’t believe that. And if you feel that you can no longer read my books or follow my blog because of my religious beliefs (or non-beliefs), you can keep that to yourself, too. People who feel that way are just an example of what’s wrong with religion in this country (or world). Too many closed minds, too much intolerance.

And, of course, I won’t try to convince believers that they shouldn’t believe. I have a lot of respect for people who can have faith in God or religion — both of which were invented by man. If going to church on Sunday or praying facing Mecca five times a day makes you feel good, great!

But if your religious beliefs are causing you to do evil things — discriminate in employment or housing, deface or vandalize private property, or harm innocent people — it’s time to take a real look at what your God really means to you.

God is Not Great

The God DelusionI’ve been waiting for a chance to read The God Delusion by Richard Dawkins for some time now. (It’s on my Amazon.com Wish List.) I’ve listened to Interviews with Dawkins on the Penn Jillette Radio Show (Penn is an atheist) and on the NPR show, Fresh Air. Although he comes off as a snobbish elitist — it might be the accent — I do agree with much of what he has to say. Listening to his views is part of what brought me to my decision about my own beliefs. It was the first time I’d heard anyone present the atheistic view in an intelligent, educated, and persuasive way.

God is Not GreatToday, I stumbled across excerpts from Christopher Hitchens’ God Is Not Great on Slate.com. One paragraph in the first excerpt really brought things home to me:

While some religious apology is magnificent in its limited way — one might cite Pascal — and some of it is dreary and absurd — here one cannot avoid naming C. S. Lewis — both styles have something in common, namely the appalling load of strain that they have to bear. How much effort it takes to affirm the incredible! The Aztecs had to tear open a human chest cavity every day just to make sure that the sun would rise. Monotheists are supposed to pester their deity more times than that, perhaps, lest he be deaf. How much vanity must be concealed — not too effectively at that — in order to pretend that one is the personal object of a divine plan? How much self-respect must be sacrificed in order that one may squirm continually in an awareness of one’s own sin? How many needless assumptions must be made, and how much contortion is required, to receive every new insight of science and manipulate it so as to “fit” with the revealed words of ancient man-made deities? How many saints and miracles and councils and conclaves are required in order first to be able to establish a dogma and then — after infinite pain and loss and absurdity and cruelty — to be forced to rescind one of those dogmas? God did not create man in his own image. Evidently, it was the other way about, which is the painless explanation for the profusion of gods and religions, and the fratricide both between and among faiths, that we see all about us and that has so retarded the development of civilization.

This is how an intelligent person looks at religion — all religion — from the outside. And — fortunately or unfortunately — this is how I look at religion these days, too.

Needless to say, this book is now on my Wish List.

Why Tell You?

I don’t know what I’m hoping to achieve by presenting my thoughts about religion here, in this blog. I think it’s just my way of getting things straight in my own mind.

Please remember that this blog began back in 2003 as a personal journal — my way of recording the things that go on in my life and mind. I think this entry is in tune with that purpose. Years from now, I’ll look back on these words and remember what I was reading and thinking in these sad, confused times.

But maybe — just maybe — my thoughts might help a few readers clear their minds on these issues.

Leopard Postponed — What's a Writer to Do?

It’s all about timing.

Yesterday afternoon, not long after the stock markets closed in New York, Apple put a one-paragraph announcement on its Hot News page. The announcement told the world (or whoever happened to be watching that page) that because Leopard resources had been used to finish up the iPhone, Leopard would be delayed. Instead of seeing the finished OS in June, we’ll now see it in October.

Why it Matters to Me

I took the news with mixed emotions. I had begun working hard on my Leopard Visual QuickStart Guide for Peachpit Press. The book will be the eighth or tenth (I’ve lost count) edition of my Mac OS VQS, which is one of my biggest selling titles. The book is important to me; the last edition accounted for half of my annual income for two years in a row. When that book is ready to write I drop everything — even helicopter charters — to work on it.

The most important part of it is getting it done on time. When Tiger came out in 2005 only two authors had books in stores beside the brand new software on its release date: Robin Williams and me. Both long-time Peachpit authors with reputations for churning out books that satisfy readers. If Robin’s book sold only half as well as mine — and I’m not fooling myself; it probably sold twice as well — we kicked butt. It was a great reward for hard work and grueling deadlines. But I have to say honestly that my Tiger book was one of the ones I’m most proud of.

This Time was Different

This time around, things were definitely different. The software wasn’t ready yet — that was obvious in the way certain features just didn’t work right. Lots of bugs to iron out, but few developmental releases. It was almost as if Apple’s Mac OS team was overwhelmed. This announcement from Apple explains a lot. Apparently they were overwhelmed, but not by the task at hand. They were overwhelmed by being shorthanded to tackle the task at hand.

Add to that the fact that my screenshot software of choice, Snapz Pro, “broke” in Leopard. Don’t misunderstand me; it did work and it took fine screenshots. But the shortcut key to invoke it did not work — even when I fiddled with Mac OS settings and tried other shortcut keys. So, for example, there was no way to take a screenshot of a menu.

I don’t know if you’ve ever seen a Visual QuickStart Guide, but they rely on screenshots to communicate information. The book is full of step-by-step, illustrated instructions. I estimate that my Tiger VQS has at least 2,000 screenshots in it. Some screenshots show windows, others show menus. Almost every single one is less than a full screen of information. Now think of how much fun it might be to take 2,000 screenshots with something as awkward as Grab or, worse yet, Apple’s built-in screenshot shortcut keys. And then manually edit every single screenshot in a graphics program like Photoshop. Not having Snapz Pro (or something equivalent, if something equivalent exists) was going to seriously slow down my workflow.

What was even worse for me (and all other writers, I assume) was the “secret features” Steve Jobs alluded to when he first showed off Leopard. I had no idea what they were. And no one else did either. What if those features changed the way part of Mac OS X looked? All my screenshots would have to be redone. And what if the features were big enough to warrant their own chapters? Or replaced existing features? That could mean significant reorganization of the book, with changes to all the chapter and feature references. I could be working my butt off to finish a 700+ page book, only to have to redo major parts of it.

So I was under a lot of pressure. I had the ticking clock that said the software would be out “this spring.” That meant before June 20. I knew my publisher needed 2-3 weeks to get the final files printed and turned into books. That meant I needed to be done writing and editing by the end of May. But not knowing what the future would bring, was crippling me, making it difficult and frustrating to get things done.

I was not a happy camper. So when the announcement came yesterday, it was a bit of a relief for me.

The Problem with the Postponement

There is a problem, however: timing.

I had planned to work on my Leopard book for April and May. Then comes my annual secret project (which I can’t talk about until after publication) for the month of June and a bit into July. Then my annual one-month stay at Howard Mesa to get some work done on our property and knock off a few articles for Informit and possibly try to reconstruct that mystery novel I was working on (which was lost in the great hard disk crash and backup screw-up of February 2007). Then we’d planned to take a vacation to the northwest to continue our search for a new place to live. By that time, it would be September and the helicopter business would be heating up again; I already have two charters lined up for that month. Also, around that time, I’d be ready to start work on my Word for Macintosh revision.

There was a plan B for this summer, too. It consisted of me getting a job as a pilot for someone else, flying somewhere other than Arizona. I could work on my secret project while I was away and escape Arizona’s brutal heat and get to fly someplace different. I have a very good lead on a job in St. Louis (of all places) and a few possibilities in Oregon and Washington. But nothing finalized.

Now these plans for the next six months of my life are completely up in the air. Assuming an October 1 release of Leopard — this is just a date pulled out of the air; I swear I don’t know anything and if I did I wouldn’t repeat it — I have to be finished with the book by the first week in September. So I’ll work on it in July and August. While I still have my secret project to work on in June, I don’t have anything lined up for the rest of April and the month of May.

What’s even worse about all this is that I can’t work on a VQS at Howard Mesa or at a summer job elsewhere — I need a desktop computer with a big monitor to do the layout — and I can’t take a vacation when I need to work on this book. (See above for how important it is.) So my whole summer schedule is completely screwed up.

And It’s a Money Problem, Too

And since I get paid advances when I work and I don’t have anything lined up between now and the beginning of June, I’m not going to see a payday until the end of June or July. Ouch. So my finances will be screwed up, too.

It gets even worse. If the book had a release date in June 2007 (with the original release of Leopard), I’d start seeing royalties at September 2007 month-end. But because it won’t be released until October, which is after the start of the last quarter, I won’t see royalties until March 2008 month-end. That’s a 6-month payday delay for a 4-month publication delay. Double-ouch.

But that’s what the freelance writer’s life is like: a financial roller coaster.

What to Do?

Today I’ll be making some phone calls. The goal is to pin down exact dates for all of my known projects so I can decide, once and for all, if I can get a pilot job according to Plan B. And, while I’m at it, I’ll try to pick up a small book project to work on in May. (Not likely but remotely possible.)

Then I’ll get to work doing other things that I’ve been neglecting — cleaning out the condo I want to rent, washing the helicopter, organizing my office, reserving rooms for next year’s Southwest Circle Helicopter Adventure trips.

After all, life goes on.

Royalty Statements

What my quarterly royalty statement tells me.

I make my living as a writer. Sure, I do other stuff and bring in money doing it, but when it all gets down to dollars and cents, the money I receive from writing is what pays the mortgage and puts food on the table.

With a new royalty statement in my hands, I thought I’d take a few moments to explain to folks interested in writing how the royalty part of writing works and what can be learned from a royalty statement.

How a Typical Writer Receives Income

Money from my writing work comes in three ways:

  • Payments for articles. When I write an article for publication, I normally get a check within 2 to 4 weeks of publication. The amount is agreed upon in advance, so I know what to expect but not exactly when to expect it.
  • Advances for work in progress on books. When I sign a book contract, it includes a payment schedule for advances. I like my advance paid in three or four installments that are due when certain parts of the book are submitted to my editor(s) — in other words, when I achieve completion milestones. A typical arrangement might be 1/3 on signing, 1/3 on 1/2 completion, and 1/3 on completion. Depending on the publisher, the checks usually arrive within 2 to 4 weeks of the milestone. Again, I know how much to expect but not exactly when to expect it.
  • Royalty payments. When I sign a book contract, it also includes a royalty percentage. The percentage is applied to the wholesale price of the book. So, for example, if the royalty is 12% and the book retails for $20 (about average for my books), the 12% is applied to the amount the publisher sold the book to retailers (or book clubs or direct order customers) for. A good rule of thumb is about 50% off the cover price. So I’d get 12% of about $10 or $1.20 per book. This royalty rate is applied to all sales of a title to come up with a royalty due. The amount of advance is then subtracted — remember, that was an advance on royalties — and if the result is a positive number, the book has “earned out” and I get a royalty check. My publishers pay royalties quarterly, although not on the same schedule. I know exactly when a royalty check will come — well, within 3 days of an exact date — but I never know how much I’ll get.

After doing this for 15 years, I’ve come to think of advances as my “bread and butter,” payment for articles as “fun money,” and royalties earned as “icing on the cake.” I won’t write a book unless the advance is enough to cover the amount of time and effort I put into writing the book. (I turned down two low-advance projects just last year.) This way, if the book doesn’t earn out, I’ll still make enough to keep paying the bills. If it does earn out, great. And since I don’t do a lot of work on articles — it’s just too much effort to get the work lined up — I don’t rely on that income for anything. That’s kind of unfortunate, because I can usually bang out one or two articles in day, so the income would really be great if I’d get get more of that kind of work.

As you can imagine, royalty statement time is a big event at my house — especially when Peachpit royalties are due. The statement comes in a big fat envelope. The reason: there are lots of pages. But one of the first pages of the package is the royalty check. And a quick peek tells me just how much icing I’ll have to spread around for the next three months.

How Many Books are on the Books?

The reason my Peachpit royalty statement comes in a big fat envelope is because there are lots of pages. The statement sitting in front of me right now is 61 pages long. I can’t even get a staple through it for filing.

The first few pages — 4, this time around — is a summary of the ISBNs covered by the statement. This list of ISBNs — 34 of them this quarter — are the books the publisher still has in its accounting system.

I need to make a distinction here between titles and ISBNs. A good example is right on the first page. My 2004 title, Creating Spreadsheets and Charts in Excel: Visual QuickProject Guide, is listed three times: the original title, the German translation, and the French translation. Sometimes translations get their own ISBN and sometimes revenue for a translation is listed for the main title. It depends on how the translation rights were sold. Also, since Peachpit is now selling PDF versions of some of my books, those versions appear on a separate line.

Still, a quick count of titles on this quarter’s statement shows 28 titles listed. Whew! Even I think that’s a lot.

In my case, the vast majority of my work these days is in revisions. So each statement might show multiple versions of the same book. This is especially true for titles that are still “alive.” For example, my America Online: Visual QuickStart Guides (a 2-part — Macintosh and Windows — nightmare completed for version 3.0 years ago) are “dead” titles. They came out, sold poorly, and were not revised. These book are dead and buried and the only reminder that I ever did them are the author copies of each book on my author copy shelf. But my Excel for Windows: Visual QuickStart Guide is alive and kicking — in fact, I just finished the revision for Excel 2007 this week. Three editions appear on my royalty statement: 2000, 2002, and 2003. (2007 will appear on the next statement.) And my Mac OS: Visual QuickStart Guide takes up the most lines: seven editions going back as far as the edition covering Mac OS 9.

For a title to appear on the royalty statement, it must be either earning money or losing money (by returns) with a more recent edition to suck up the losses. This is an important clause in book contracts — one that’s important enough to discuss in a little more detail here. Commonly known as cross-accounting or cross-deductions, it means that returns on one title can be applied to net revenue on another. So, for example, if my share of returns on an old edition of my Excel book was $43.54, that amount could be deducted from or charged to royalties on a more recent edition. That’s normally why books stay on royalty statements for so long — there’s still accounting for them.

It was kind of a good thing that my AOL books didn’t have more recent editions. Neither title earned out, so the money I was overpaid for those books could be deducted from future editions, had they existed. Instead, the publisher cut their losses by not doing new editions (a wise move) and simply stopped accounting for the existing books when the numbers stopped coming through. The books “fell off” my royalty statement.

(If you’re ever given the opportunity to negotiate a book contract, do not sign a contract with a clause that says all of your books can be pooled together for cross-accounting. (I don’t know the exact wording of a clause like that because I’ve had it removed from every single draft contract it appeared in.) Agreeing to this may prevent you from ever getting a royalty check if you write multiple titles for the same publisher and any or them are dogs. If you’re really lucky, you won’t even have cross-accounting for the same edition of a book — I was lucky to have that situation with one of my Quicken titles years ago. But I think it’s fair to do cross-accounting with different editions of the same book, so I don’t mind signing for it. I just brace myself for the returns every time a new edition comes out.

And returns, in case you’re wondering, are returns from retailers/wholesalers, not consumers. If Barnes & Nobel buys 1000 copies of a book and sells 200 of them in the time they allotted to give the title shelf space, 800 copies come back. That’s a bad thing for the author.

What the Summary Numbers Mean

Still with me? Here’s a bit more that the summary pages tell me.

For each ISBN, the summary page has 6 numbers:

  • Previous Balance is the amount owed to me (positive number) or the publisher (negative number) for the ISBN. There usually aren’t any positive numbers; if the publisher owned me money, they paid me last quarter. So books that are earned out show zero in this column. If I owe the publisher money — for example, the book hasn’t earned out or subsequent returns have put the ISBN in the red — that number appears as a negative value. Zero is good, negative is bad.
  • Earnings/Subsidiary Rights Earnings is what the book earned me during the quarter. That’s the royalty calculation applied to net sales. Positive numbers means they sold more books than they received in returns. Negative numbers mean they got more in returns than they sold. Positive is good, negative is bad.
  • Credits/(Deductions) is the amount paid out during the quarter for advances or, if the author is paying for indexing, the amount paid to the indexer. I’ve never seen a positive number in this column.
  • Cross Deductions is where they take returns from one title and apply them to royalties earned on another title. So, for example, if the net earnings on my Word X book were -$53.47, that amount would appear as a positive value in this column for that ISBN and a negative value in that column for a later edition — perhaps my Word 2004 book. If you add up the cross-deductions column, the net amount should be zero.
  • Payment Due is the net amount owed to me for the ISBN. This number is either zero or a positive number.
  • Balance Forward is the amount that needs to be earned out to get more royalties on the ISBN. It’ll be zero if there was a payment in the previous column or a negative number if zero was in the previous column. That value is carried forward to the Previous Balance column in the next statement.

Of course, this is the format Peachpit uses. Other publishers may use other formats.

So when I get a royalty statement, the second thing I look at is the summary. (The first is the amount of the check, of course.) The summary tells me which books are earning money for me. That’s usually current editions of books. This is where I can see at a glance whether a new title has earned out. I can also see which books are earning me the most money — the titles with bright and happy futures. The bigger the payment due on a title, the more likely that title will be revised in the future. (Unless the software publisher decides to kill the software, as Adobe did to PageMill years ago. That book was doing very well when it was killed.)

Sometimes I get pleasant surprises. For example, my Excel 2002 book is still selling. That book was published five years ago and it earned $262 for me this quarter. Okay, so that isn’t enough to host a big party, but it’s a nice thing, a good thing. After all, the average life of a computer book is 18 months. So to have one that’s still bringing in a few bucks for me after five years is great.

The summary statement also tells me which titles are dead. These are the titles with previous balances that are negative numbers and no revised editions to earn more revenue. Sometimes these titles have ugly negative numbers in the Earnings column, indicating returns. My QuickBooks Pro for Mac book is in this situation. Although it’s the only title covering that software, there simply aren’t enough users interested in buying a book to make the book earn out. So when my editor says the publisher is not going to revise the title, I can look at this royalty statement and understand why. The book is dead.

Want more detail? The summary pages are also a table of contents for the 57 pages that follow them. That’s where I can find information about units sold, subsidiary rights (like translation rights), and where the books were sold: U.S., Canada, Export, etc. To be honest, I don’t look at these pages for every title. Heck, I have enough to do in a day.

What I Learned this Quarter

Looking at the royalty statement is like peering into a crystal ball. I learned that there are certain topics I probably won’t be writing again and other topics I’ll be writing about for years to come. I learned which of my books is doing best for me (still Tiger, after two years!) and which ones I might want to promote a bit more to liven up.

But with 61 pages to review, that’s about all.

The Bookwoman's Last Fling

Disappointing.

Two or three years ago, I discovered John Dunning’s work. Dunning writes mysteries with a series character named Cliff Janeway. Former tough cop turned bookshop owner/operator Janeway narrates the tales of the book-related mysteries he solves. Along the way, the reader learns a little about collectible books and the world of bookshops.

Being the A.R. person I am, I always try to read an author’s books in the order in which they were written. This is extremely easy to do when borrowing books from the local library, since the librarians number each of an author’s books chronologically, right on the spine. In most cases, they’re even shelved in order.

The Sign of the BookThe Sign of the Book was Dunning’s first Janeway book. I don’t remember why I picked it up, but once I started reading, I couldn’t stop. It was some of the best mystery fiction I’d read in a long time. A good plot, good characterization, and good dialog. I went through it quickly and felt extremely satisfied — but ready for more — when I was done.

I then began reading the rest of Dunning’s Janeway books. The second wasn’t quite as good as the first, but it was still very good. The third wasn’t quite as good as the second. That made it above average. The fourth wasn’t as good as the third. I was definitely seeing a pattern here. It was as if Dunning was steadily losing his touch.

The Bookwoman's Last FlingThe Bookwoman’s Last Fling was a disappointment, plain and simple. It’s difficult, in fact, to believe that it was written by the same author who penned The Sign of the Book.

The book’s plot was contrived — Janeway makes conclusions without proper evidence (a violation of the mystery writers’ rule of “fair play’) and his actions based on those conclusions steer the plot. For example, early in the book, he decides that he needs to spend time at a certain racetrack where a woman who died 20+ years before had spent a lot of time. Why? There’s no clear reason provided. Once he gets there, does he start doing the logical thing — asking questions? No. That comes later, after more illogical activities. Clearly, the character is driven by the author, not by the circumstances he’s put into.

The dialog was flat and unrealistic. One of the things I liked best about Dunning’s first Janeway book was the snappy dialog. It flowed and was fun to read. As a reader, I felt alone with the characters, “listening” to them talk. In this book, Dunning seems to be working too hard to get those words out, and that effort is quite apparent to the reader. I’m not alone with the characters; I’m alone with the author, who is trying desperately to communicate what his characters may or may not have said. And although I usually feel that an author’s words are sacred and shouldn’t be over-edited, an editor could easily have cut 30% of the dialog and the reader wouldn’t have missed a thing.

The dialog was also difficult to follow. I’ve read a lot of novels, but I’ve never had so much trouble keeping track of who was speaking. Many, many quotes are unattributed to their speakers. That wouldn’t be a problem if Dunning had stuck to the common writing convention of starting new paragraphs for each speaker. But in some instances, the same unattributed speaker speaks in two paragraphs in a row or the attribution is simply unclear. Never before had I wished to see a few more “he said” or “she said” phrases.

Characterization was also flat and lifeless. The characters didn’t come off the pages. Dunning told you their traits; except in a few instances, he didn’t really show you much. Character relationships weren’t brought out, either — even between Janeway and his lady friend. What is their relationship, anyway?

I feel bad about writing such an unfavorable book review for an author whose work I’ve admired in the past. But I have a sneaking suspicion that Dunning wrote this book — and likely some of his previous books — under pressure by editors to produce another big seller. Apparently, he didn’t have the book in him — at least not when he wrote it.

I believe that a writer has to be internally driven to write a book in order to produce good work. External pressures can’t squeeze a book out of an author who just isn’t in the right frame of mind to produce. In reading Dunning’s later work, I get the feeling that he just wasn’t ready to write when he did.

digg IT

A new plugin being tested here.

Although I have my doubts about digg, I’ve always been curious about whether my posts have ever been “dugg.” I’ve often seen buttons with digg counts on other WordPress Web sites. I figured it was time to try installing one on this site.

digg what?

digg, in case you don’t know, is a social bookmarking site that’s pretty popular among blog enthusiasts. You sign up for a free membership, then “digg” blog posts you like. If the post has never been dugg, you can be the first to digg it. Otherwise, you can just add your digg to the count of existing diggs. You can also add comments about the post.

Posts with lots of diggs — generally more than 100 — get lots of visits, mostly from people who monitor popular posts on the digg site. So, for a blogger, being dugg could be a good thing.

I say could be because if you’ve got a lot of diggs, your post could become so popular that hits exceed your bandwidth. That happened with podiobooks.com, which I learned about today. A note on its site says:

We’ve been Dugg and Lifehacked in the last 24 hours, and the site is experiencing a little oddness from time to time. We’re working on getting things stabilized.

That’s when you can get the site. You’re just as likely to get a Server Error 500 when you attempt to access. Oops. Hopefully, things will calm down for them enough for their server to handle incoming requests.

The Plugin

Getting the digg button on a post is a matter of installing a plugin and modifying the WordPress theme’s template code to add a new function.

I needed to find the plugin, so I used by friend Google to search for digg wordpress plugin.

I first found Digg This, which was at the top of the list. I wasted no time downloading and installing it. Unfortunately, I couldn’t get it to work. And when I scrolled through the list of comments, I discovered that I wasn’t the only one.

I decided to keep looking.

I then found digg IT (which may have been called Digg This in a previous incarnation). I downloaded and installed it. It worked immediately, perfectly. If I’m still using it as you read this, you’ll see it at the top right of each post.

(I say if because I might not keep it. Although it works like a charm, seeing so many posts with 0 diggs is kind of depressing. I have a post that’s been read over 3,000 times and still has 0 diggs. [sigh] You can help cheer me up by occasionally digging my posts.)

The installation required a single line of code to be inserted in The Loop, right before the < ?php the_content(); ?> tag:

< ?php if(function_exists(digg_this)) { digg_this('', '', '', ''); } ?>

It’s a nice piece of code because it checks to make sure the function exists before actually calling it. So if the plugin fails or is not compatible with a future version of WordPress, your site visitors won’t see an error message. I like neat code like that.

Unfortunately, the documentation does have a tiny error. It tells you to insert the code in your index.php file. If the < ?php the_content(); ?> tag for your theme isn’t in that file, those instructions could confuse you. In my case, that tag is in my post.php file. So you do need to have a little knowledge about your theme’s template files to install it properly. Just open them all up until you find the < ?php the_content(); ?> tag and you can’t go wrong.

Anyway, if you’re posts are dugg or you want them dugg, you might want to give this plugin a try. You can’t beat it for ease of installation and use.

March 26 Update: I removed the digg count from my pages. The zeros were really getting to me. If the site ever starts getting diggs on a more regular basis, I’ll put it back. For now, the code is just commented out.