Archive for the ‘humor’ Category

How I Talked Myself Out of a Kindle

Monday, March 23rd, 2009

It takes me a really long time to buy a gadget. Over the course of months I deliberate whether I really need the device and, if I do, what options I should get. The current object of my rumination is the Amazon Kindle 2
and, right now, the pendulum is on the “not buy” side of the swing. Here are the arguments that are keeping it there.

  1. I like to share books with my friends and family. The exchange of books can be a nice social experience. You loan or borrow a book and you have at least one person you can discuss it with.
  2. I buy used books. Used books can be a great deal. I like to browse used book stores and tags sales to find interesting books at a reasonable prices.
  3. The paper book just may be the culmination of reading technology. More durable than a papyrus scroll, cheaper than liquid crystal, what could be better than paper?
  4. My personal library is a carbon sink. You see an overloaded book case, I see hundreds of pounds of carbon not released into the atmosphere. A Kindle would be powered by a coal plant on the other side of town.
  5. I would rather read than talk about my reading device. I have hardly ever seen anyone actually reading a Kindle. Most Kindle owners that I see are too busy getting interrupted by strangers who have an opinion about the future of eBooks. A shy person like myself appreciates the camouflaging qualities of a nice boring looking paper book.

There you have it; those are my reasons. They are working for me right now but, in case you are not convinced, you can click through this Amazon Associates link
and put a little money in my Kindle fund (because that I know that I will eventually cave).

Talk about lock-in! How about a WordPress tattoo?

Thursday, March 12th, 2009

Lorelle VanFossen posted the first known permanent WordPress tattoo. I guess (tattoo recipient) Ed Morita didn’t read my post on CMS exit strategies. As with most CMS implementations, the feedback has been mixed. Comments on Lorelle’s blog range from “Woah! I think it’s a good tat! And it is a great location” to “Oh dear I hope that is fake cos that is the lamest tattoo ever!” However, unlike most CMS implementations, which are planned to be in place for less than 5 years, Ed’s tattoo should last a lifetime.

RFP Horror at the RNC

Tuesday, March 10th, 2009

tre_cms
How could the RNC not select a CMS called The Red Elephant?
(this image is copyrighted by Red Elephant ICT & Internet Services)

Gregor Rothfuss sent me a link to a report about a ridiculous CMS RFP issued by the RNC. As I have written before, the traditional RFP process is totally broken. Here, the RFP asks for innovation around sketchy buzzwords that are meant to be requirements yet still asks for a fixed bid. I wonder how the RNC could avoid selecting a CMS called The Red Elephant?

In my Web Content Management Selection workshop at last year’s Gilbane Conference, I told a story about a fictitious botched selection process for an imaginary website. This may be one of those cases where reality is better than fiction so I am thinking that the RNC RFP should be my anti-example when I teach the selection workshop this summer.

Sex doesn’t sell… at least not for FatWire

Thursday, December 4th, 2008

I regretted having to leave the Gilbane conference early because I missed seeing so many friends and colleagues but I had no idea I was missing this FatWire gaff of showing the Playboy as their reference site. I am sure that demo would have been compelling to some audiences but it flew like a lead balloon at the Gilbane. The worst part for FatWire was when the CEO told an offended audience member that she was wrong to be offended. I guess the age-old rule of presenting still holds: know your audience. You can see some immediate reactions on Twitter.

Developers in Pain

Tuesday, October 7th, 2008

Just had to post this….


Developers In PainFunny bloopers R us

Wikis Not Word! Gaining adoption through psychological warfare

Wednesday, August 27th, 2008

Your company has a perfectly good wiki but your (otherwise intelligent) co-workers insist on emailing you Microsoft Word documents to review. Your gentle guidance has been ignored. Your snarky comments have been equally ineffective. What do you do? I suggest the following method. Try it (at your own risk) and let me know how it works.

A co-worker has sent you and four or five other colleagues a MS Word document that summarizes some research that he did. The document contains some simple headings and paragraphs. You have a lot of ideas and feedback to give but, rather than give it all at once, you trickle it out and have your co-worker feel the pain of merging your edits.

  • Draft 1: Re-Format. Don’t really change anything, just format the heck out of the document. Change the styles around. Send it back with a cryptic filename like [irrelevant name]_[your middle name]_final.doc. Mail it with a note saying that it looks good and you had some slight wording changes. Leave it up to your co-worker to figure out that nothing has really changed.
  • Draft 2: Re-Organize. A day after the first draft, take the original document you received and re-organize it. Re-order the sections and a few sentences here and there. Make sure that you turn on “track changes” so that the whole document is a multi-hued mosaic of change notifications. Name it [original filename]_new.doc. Send it with a note saying that you discussed it with another colleague and got some new ideas but “it is really coming along!”
  • Draft 3: Edit. This is the version where you provide your real feedback. Start with your Draft 1. Make your edits. Name it [original filename].doc. Send it with a note saying how excited you are about this project and have been “thinking about it non-stop.” Schedule a meeting to go over it and ask that your colleague send out a merged final draft for everyone’s review. During the meeting, walk through everyone’s feedback. By this time, your colleague is probably totally fried and is ready for a new way of working. At the end of the meeting, innocently say something like “you know, this might have been easier if we had worked in the wiki.”

This method works even better if you have a co-conspiritor working with you doing the same thing. During the process, watch out for signs of mental instability or fragility and remove all sharp objects from the office. Make sure that the Employee Assistance Program posters are visible and well placed.

All humor aside, sometimes the only way to change people’s ingrained behavior is to offer an alternative that is substantially easier. It has to be a big improvement because old habits are hard to break. Starting to use a wiki can be hard for people accustomed to Microsoft Word. They will initially get frustrated and resort to what they know. If you can’t eliminate the learning curve of a wiki, you can expose the inefficiency of collaborating without one. The next time they launch Word, they will remember their painful experience and think twice.

Design Gone Wrong

Wednesday, July 23rd, 2008

Anyone who has worked on a web design project can probably appreciate this.

Design Coding

Friday, April 4th, 2008

For more in depth (non musical) best practices check out Non-Linear Creations’ excellent whitepaper SEO and CMS: Best practices to make your CMS SEO-friendly

Now THAT is a Domain!

Thursday, September 13th, 2007

I was Skyping with someone a couple of days ago and he was referring me to a URL that he decided it would be better to type. One reason was it was not in English and I have no foreign language skills. The other reason was the URL was http://www.maatschappelijkverantwoordondernemen.be. Now that is a URL. I recently saw a presentation by David Esrati from The Next Wave where he talked about his 80-40 Rule. The basic idea is that URLs are less important because 80% of browsing starts in the search box. 40% of users are so clueless that they type the URL in the search box. If this is true, having an awkward domain name is not so much of a problem. Social bookmarking and blogs probably help too. But I assume that there are limits to acceptable awkwardness.

BTW, kudos to J Rulnick for having the foresight to register chargoggagoggmanchauggagoggchaubunagungamaugg.com after the longest place name in the United States! He gets the 80-40 rule! I think?

When Good Content Turns Bad

Tuesday, June 19th, 2007

We all dream about a unified view of content but maybe this goes a little too far?