Skip to main content

Two Hex and a User

I wanted to post two related hex graphs that give us some good mind food to munch on while we work. The first is more general and tells us seven points of User Experience Design. Take a step back and ask yourself:
  • Useful - Is the software even useful?
  • Usable - What it does is useful, but is it usable?
  • Findable - Can the user find what they need to use?
  • Accessible - Can all the users access it?
  • Desirable - Do the users want your 1 software?
  • Valuable - Is your software valuable enough for the user to retain?
  • Credible - Does the software look fake or are you trusted?

Up second, adapted from the original for social software purposes. We're beginning to see more and more social software, and the seven elements given here fit nicely into all the services I use.
  • Twitter - Presence and sharing (of presence) and conversations (about presence).
  • Blogger - Conversations, reputation (comment count), sharing (ideas), groups and relationships (informal; by linking).
  • MySpace - I hate MySpace, but I use it anyway. Relationships and groups are obviously the focus.
I take this in and consider how we break up these elements into different services, and the focus of each service on one or a few elements benefits us. Twitter does great at what it does, etc. But the separation also harms us. The little widgets we can put on different places to connect the services together only go so far. I have too many feeds, but obviously I can't send all my "tweets" through this feed, as is. So we're getting good at breaking things up, but I'm really waiting for how we'll bring it all back together.



1: Two separate emphasis given.


Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro