Home

Advertisement

Customize

The forehead mashing method

I liked this blog entry from Planet KDE. That entry reminded me to talk about one way I like to think about how to improve the user experience with software - and that is by what I call the "forehead mashing" method.


This is where as you're developing software, write out a few problems that you're trying to solve. Then, for every step the user is required to make - for every dialog that pops up, for every few seconds of keystrokes, every dialog to click, every checkbox to check...lower your head onto the desk and hit your forehead.


You don't have to do this with a lot of force. Just enough so that you feel it.



This calls for several head-desk hits



One of the top things that will quickly make your forehead sore are Wizards/Assistants. The way I think of these is that the programmer is so proud of their work and they think it's so awesome and complicated that they want you to acknowledge it.


What if programmers inflicted these kinds of things on ourselves? Say in gcc.



If you all keep making wizards, I'll create this patch for GCC


It's not just wizards of course that are the source of pointless user time spent reading text and clicking buttons; random dialogs are another source. Often with some thought, it's really not hard to reduce and simplify.



This is davidz's theme, don't blame me


So I promised in the comments in my previous post that I would do something to reduce the pain from the notification bubble I added; to keep the universe in balance as it were. So I'm happy to say that in Fedora rawhide now, the above dialog is no more. It was just a bad idea, and you will never see it again.

Comments

(Anonymous)

User Frustration

I feel sorry for the poor programmer who tries to find the "Next" button on your gcc dialog. Searching the man page found that if, during the parsing stage, gcc doesn't like the way your code looks, it makes small changes to the wording of the gui just to annoy you. I just wish they would have chosen more logical names - "SIG_ABORT" and "CONTINUE EXECUTION" or something like that.

(Anonymous)

My Mother always told me...

As my Mother always told me: "If you don't have something good (actually nice, but same sentiment) to say, DON'T SAY ANYTHING.". We would be wise to follow that advice, eh?

(Anonymous)

Thank you

Nice, thank you.

Next stop, doing something about Network-Manager-Gnome making a popup that is has connected to (my own) WLAN each time I turn the computer on? I really can not see any extra value of it, although it irritates me greatly.

Your gcc wizard

talks about clicking Next when the button is named Forward. Obviously your patch will get rejected this way.

If you link to the source code I will send you a patch.

(Anonymous)

Just wanted to say

Tahnks for posting

(Anonymous)

Cool text.

thats it, brother

(Anonymous)

thank you

thats for sure, dude

Advertisement

Customize