[tahoe-dev] barriers to using tahoe

Raoul Duke raould at gmail.com
Mon Feb 1 18:53:45 UTC 2010

On Mon, Feb 1, 2010 at 9:40 AM, EdPimentl <edpimentl at gmail.com> wrote:
> Define the user optimal user experience ...

i think that phrase is fraught with peril.

there is no optimal user experience in some sense; there are too many
different needs to balance to define anything. in my mind, good
usability is all about making trade-offs over time across all possible
use cases. the best you can write down is something like "the user can
successfully accomplish tasks, and the user reports they are happy
with the experience." if you try to get more detailed than that (with
more than like 1 single user) you are going to quickly get into
conflicting interests, abilities, goals, etc. which all have to be

in other words: if there is not an experienced user experience person
working on the project, then the chances of getting something as
complicated as this to be an "optimal user experience" is nil. hire
somebody :-)

no i'm not a ux person by trade, only by end-user-suffering perspective.

More information about the tahoe-dev mailing list