Older blog entries for CharlesKerr (starting at number 1)

I haven't seen any mention of aaron's UI guidelines except for once on IRC, but I liked them so much that I put them near my monitor at DayJob. So, in the unlikely chance that someone's reading this diary, here they are:

  • Users want predictable behavior.
  • The intuitive interface is the one that mimics the user's expectations.
  • Users do not customize. The best option should already be chosen for them.
  • Users do not care about underlying structure or back-end implementation.
  • Users do not read manuals.
  • Users do not read instructions.
  • Users do not read dialog boxes or warnings.
  • Users do not read status bars.
  • Users do not read any sentence longer than four words.
  • Users do not see things that are obvious to the developer.

Good stuff. The first two items echo what Joel Spolsky says in UI Design for Programmers book, and item three is what Havoc's been saying about "crack" features.

Wheee, I've finally signed up for an advogato account. Should've done it sooner; "charles" was already taken.

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!