Skip to content


Musing about Agile error messages

For most of my adult life, I’ve been bemused, perplexed, sometimes irritated and occasionally completely taken aback by the error messages spewed out by the applications we build and use. Over the last twenty-five years or so, I’ve watched them improve, but at speeds that make glaciers look agile.

Today, while looking at technorati, I saw this:

Something is wrong! We know about it, and are working furiously to fix it. Please check back later and probably everything will be back up and running.

Great stuff. You may not think it’s perfect, given that it doesn’t actually say how long it will take to get fixed. But I like it. It is open, conversational, simple, honest and brief. I tend to think that the uncertainty implied in the message is actually a good thing; it made me think … could we expect to see error messages that are Agile in nature, improving by iteration as better information emerges/is discovered?

Who knows, this may be a leading indicator of the paradigm shift taking place in the applications and services space today.
My thanks to all at Technorati.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

Popularity: 1% [?]

Posted in Four pillars .


4 Responses

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.

  1. rama says

    Hi JP. Funny post! I been ping-ing technorati for the last 6 weeks, with no updating happening. I wrote to them repeatedly, with no substantive response. Now I understand! Best, chutki

  2. PaulSweeney says

    When we were releasing our service (Interactive Voice Notification) to our beta customers I can hon estly say that the number one cause of “annoyance” was when an error message wasn’t “specific”. For instance if a call could not be delivered, don’t just say “call could not be delivered!”. Customers wanted “the number specified was called but the person did not pick up the phone!” A simplistic example perhaps, but even for simple services such as our own, the need to get pretty specific with error and exception handling reporting was a big take away.

  3. rama says

    Hullo again JP. I thought you might have a refreshing and insightful take on the finding from the Stanford University School of Medicine’s study that “the USA could be rife with Internet addicts as clinically ill as alcoholics”. See:

    http://thestatesman.net/page.news.php?clid=3&theme=&usrsess=1&id=133525

    I thought you might also be interested to read:

    http://thestatesman.net/page.news.php?clid=4&theme=&usrsess=1&id=133529

    Best, chutki

Continuing the Discussion

  1. Confused Of Calcutta » Blog Archive » Opensource makes you Responsible linked to this post on October 20, 2006

    [...] There’s a strange kernel to this post. Recently I posted something about Agile error messages, and Kevin Marks, while talking to me about it, took me on a tangential journey to a post at chuqui 3.0, headlined Why Do Businesses Shy Away From Open Source? [If you have the time, take a wander round Chuqui. Chuq van Rospach seems an interesting guy; and any blog with a tagline saying “And I’ll keep reinventing myself until I get it right” has got to be worth a read. Thanks for the heads-up, Kevin]. [...]



Some HTML is OK

or, reply to this post via trackback.