"Developer Experience" as an Aspect of Quality

Recently, a leader within my organization sent excerpts from Designing Great Web APIs around for reading, reflection, and discussion. The subtitle of this book is "Creating business value through developer experience."

James Higginbotham, the author, asserts that "entire markets are emerging where APIs compete for the attention of developers." I agree with this, and it tempts me to include this in my big list, Aspects of Quality. I could tuck it under 'invites repeated use', but I'm not sure that calls this out specifically enough.

As we design systems that are more open, made more as the middle-man, meant more for consumption of primaries, this becomes a critical factor in judging quality.

If we do look to test this specifically, what kind of test would it be? Usability? Desirability? Something new?

For now, I will think on these things, and look forward to your thoughts.

Ctrl + Alt + Delete was a mistake: Bill Gates

... but I must admit, I've developed some fairly impressive finger positions to do the one-handed login.

Finally:  Bill Gates admits Ctrl + Alt + Delete was a Mistake

h/t funnylifestories.com

A fun fusion of gaming and career

One theme that keeps popping up in my study of user experience is that of achievement reward systems.  You look at any task you would like a user to perform, and, no matter how mundane, you reward their achievement in some way.  This can even be something as simple as a meaningless list item in a long list of meaningless list items.

Companies have flirted with using this approach in real world activities, such as teeth brushing and bike riding.

In my mind, the three most important characteristics of a successful achievement reward system are:

1. Show users what is possible to achieve (list the achievements possible, and a clear explanation of how to achieve them)
2. Show users where they've been, what they've achieved, in a way that is satisfying.
3. Make sure the achievements can be obtained at a reasonably consistent and fast pace (you don't want people getting bored while trying to achieve one thing... keep the rewards flowing)

With this in mind, I got a kick out of the following link.  It is a list of achievements toward being an expert web developer, presented like a role-playing game skill tree.  You developer yourself along this tree's branches, with the end goal of becoming the web developer you desire to become.  This page even lets you choose your character portrait and name.  Great stuff.  I hope you enjoy.

Becoming a web developer via RPG skill tree