How NOT to Provide Instructions to Your Web Developer

Hint: Embedding images in a Microsoft Word file is never a good idea.

WheelsYears ago, I received a flyer in the mailn about a replacement for my helicopter’s stock ground handling wheels. For those of you who don’t know, you move a helicopter around on the ground by attaching wheels that lift the skids off the ground so you can push it. The stock wheels on my helicopter — then an R22 — were too small for me to clear the runners for my hangar door. These larger wheels — called “Big Wheels” — would give me the extra clearance I needed to get over the lip.

Trouble is, I didn’t want to spend $450 on a set of wheels, sight unseen.

So I offered the manufacturer a free Web site in exchange for the wheels. Being a guy who wasn’t particularly Internet savvy, he said yes. And thus began our relationship.

In the ten or so years since then, Walt has given me numerous items of ground handling equipment to test out. Some of it I really liked — like the Big Wheels that he gave me for my R22 and, later, for my R44. Others, not so much — the original tow bar design, for example, wasn’t quite beefy enough to tow my R44 from my hangar to my departure area some distance away at the airport. But it was all great quality stuff that I was pleased to have the opportunity to use and show off. In exchange, Walt got a respectable-looking website, first coded in HTML and then upgraded as a WordPress-based CMS. Lots of pictures — some of which I’d taken with my helicopter as model; the one above is an example. (Yes, my first helicopter had white skids).

The only thing that kind of bugged me over the years was the way Walt requested updates to the site. He’d sometimes send random photos with notes. Sometimes I’d make a requested change and then he’d respond with another change to the same page. I’d get bursts of email messages from him with new content. It got to the point that I’d usually wait a week or two after hearing from him to make sure there wasn’t anything else on the way. That led to me forgetting to take care of things for him and him politely reminding me and me finally getting it done.

Please understand that I don’t mind updating his site periodically. It’s not as if he does it every month — or even every year. It really isn’t (or should’t be) much work. And I use the wheels regularly. I don’t feel as if I’ve done enough work to cover the cost of them yet. After all, it isn’t as if I created some super spectacular custom solution for him. It’s not as if I spent weeks of my life developing and maintaining his site. And he really is a nice man who makes a great product.

About a month or so ago, I got an email message from Walt’s wife. (I didn’t even know he was married.) She wanted to know the best way to request changes. I told her to put them all into one email message.

The email messages started arriving a while later. Note that I used the plural form of the word message. I was busy with other things — a book, travel, etc. — and I didn’t take a look at them right away. She emailed me to confirm that I’d received them. I said I had and would get to it as soon as I could. She waited another week and then sent another email with a note saying that she’d put all the changes in one document, as I’d requested.

Attached was a Word document.

And then I looked at the other email messages. They all included Word documents, too.

I don’t recall asking for a Word document and I know damn well I never told her to embed the images in a Word document. There are few things as painful to me (or likely to anyone else) than removing more than 50 images from a Word document file.

EditsBut what’s worse is that she created it with Word tables and used notes inside the table cells to indicate which images to keep and which ones to remove.

Yes, that’s right — she also sent me images I already had. Images that were on the website.

And did I mention that the images were all different sizes and resolutions and proportions? They look the same here because she resized and cropped them in Word. But they’re all over the map when it comes to size and some of them are as tiny as 2-1/2 inches wide at 72 dpi. This is supposed to replace images that were at least 6 inches wide at 72 dpi. Do you know what they look like when I try to scale them up?

But it’s the inconsistent use of little down-pointing arrows and the positions of the images that I’m struggling with. Is she pointing to a replacement or the one I’m supposed to delete?

Understand that she didn’t reproduce the page the way it appears on the website. She didn’t label them the way they are on the website. From what she’s sent, it’s not even clear whether she’s introducing new products, removing old products, or just playing a really mean joke on me.

Don’t get me wrong. I like Walt and I love his Big Wheels. (Seriously: if you have to pull an R22 or R44 or R66 around, these are the wheels you need.) He’s a nice person and his wife seems very nice, too. It’s extremely difficult, however, to get the job done with what they sent. And not to scream in frustration.

I know they’re doing the best they can. But I also know that this could easily be a post in Clients from Hell.

So now I’m waiting for her to get back to me with more information and possibly some newer, larger photos so I can finish up, take a deep breath, and go have a martini.

Do you understand now why I don’t do websites for other people anymore?

New Subscription Feature Delivers Full-Text Content from this Site

Another way to get new content here.

A while back, I switched to summary post format for RSS feeds. I did this, in part, to stop the feed scraping activity that was violating my copyright to the contents of this site. This disappointed a lot of people. They apparently preferred reading content in their RSS reader application or via email instead of coming to this site.

While I understand the convenience of reading sites in a feedreader — I use a reader on my iPad to keep up with my favorite sites — I don’t have enough subscribers to justify putting my content at risk for scraping. And I figured that people who really wanted to read what’s new here would take the extra effort to follow the link in their feed reader or email notification to go to the site. Hell, it only takes one extra step.

In the meantime, the WordPress folks added a new subscription feature that makes this kind of moot — provided you like to read new content via email. They’ve added email subscription capabilities. Extremely easy for bloggers to configure, it adds a subscription widget to the sidebar. All the reader has to do is enter his/her email address and click a button. Moments later, an email confirmation message arrives in their inbox. Click the link in that message to start the subscription.

Sample MessageThe resulting email messages are nicely formatted to present the entire contents of the blog post. This is an example from earlier in the week; I subscribed to test it out. I chose the HTML format, but there’s also a plain text format. This even looks good in a mobile device like an iPad.

Links in each message give you easy access to settings and the ability to unsubscribe at any time. In addition, all of your subscriptions to WordPress sites are maintained in the same place, so it’s easy to modify settings for all of them at once. In addition to email format, you can also specify delivery frequency: immediate, daily, or weekly. The Delivery Frequency settings lets you specify what time of day or day or the week you prefer. You can even click a check box to temporarily turn off the email messages when you think you might be too busy to read them.

I think this is a great compromise between full-text RSS feeds and summary feeds. After all, if you want the convenience of new content delivered to your mailbox, you have it. My content is protected from feed scraping because it never appears in an RSS feed. But if you prefer to check in via RSS reader, you can continue to do so as you may already be doing — you’ll just need to take the extra step of clicking a link to read the full text of a post that interests you.

What do you think? Your comments are appreciated.

Battling Comment Spam

An interesting — but unfortunate — statistic from this site.

One of the biggest challenges to bloggers who allow comments on their blogs — other than dealing with immature, know-it-all asses who can’t write a civil sentence — is comment spam. It generally comes from three sources:

  • Automated spambots that are programmed to post comments on blogs. This accounts for more than 90% of the comment spam out there.
  • Real people who manually post comments that promote their products, services, or websites.
  • Pingbacks from blogs built by scraping content from other blogs, primarily to attract hits to other links on their pages.

I wrote about comment spam extensively on my Maria’s Guides site when I was regularly providing fresh content about WordPress. If you’re a blogger, you might find the following posts there interesting:

Spam vs. Ham on An Eclectic MindWordPress’s anti-spam tool, Akismet, does an excellent job of catching and filtering out spam so I don’t really need to see it at all. It also provides statistics about comments. This morning, while looking at these stats, I discovered that a full 98% of all comments posted on this blog are spam — or about 4,000 to 10,000 spam comments a month — leaving only 2% as legitimate comments (or “ham,” a term used by Akismet).

If this percentage is about the same on all blogs, it’s easy to see why so many bloggers elect to either turn the commenting feature off or require registration for commenting. (Note that registration doesn’t always help; some spambots can also register an account and then manual intervention is required to identify and delete those accounts.)

Comments are moderated here for two reasons:

  • Aksimet doesn’t catch all spam. It misses, on average, about 10 spam comments a month.
  • Akismet can’t identify abusive comments.

I have a zero tolerance approach to spam and abusive commenters and don’t want to see any of it on this blog. So I manually review all the comments that Akismet approves before allowing them to appear on this blog.

June 30, 2014 Update
I’ve finally gotten around to writing up the site comment policy on a regular page (rather than post) on this site. You can find it here: Comment Policy.

(If you believe that deleting comments is censorship or somehow violates your freedom of speech, read this and this.)

Personally, I’d like to see a higher percentage (and number) of legitimate comments on this blog. I like when good conversations get going among readers. I can think of two posts offhand where reader comments have added real value to what I’ve written: “The Helicopter Job Market” and “Why Groupon is Bad for Business…and Consumers.” I write from experience and my experiences are limited. When readers share their own thoughts based on their experiences, they provide more information for other readers to draw upon. They help round out a discussion. And as long as they don’t get rude or abusive to me or other commenters — or are obviously commenting to promote their own product or service (i.e., spamming) — I don’t care if they disagree. Intelligent, civil debate based on facts is encouraged.

But while comment spam is obviously a serious problem for all bloggers that allow comments on their blogs, I have it well under control here.