4 ms·
I think the "Unix Philosophy" is way ahead on this one. http://www.faqs.org/docs/artu/ch01s06.html http://www.faqs.org/docs/artu/ch01s06.html Rule of Least S
by sp332 13y ago
I think the "Unix Philosophy" is way ahead on this one. http://www.faqs.org/docs/artu/ch01s06.html http://www.faqs.org/docs/artu/ch01s06.html
Rule of Least Surprise: In interface design, always do
the least surprising thing.
Rule of Silence: When a program has nothing surprising to
say, it should say nothing.
Rule of Repair: When you must fail, fail noisily and as
soon as possible.
- dllthomas 13y agoYou can minimize surprise by always immediately crashing. There will be a slight learning curve, but rather quickly a user will never be surprised by your UI again.
- austinhutch 13y agoThis is interesting, can you elaborate or provide and example? Thanks!
- dllthomas 13y agoIt was meant to be amusing, not interesting... The idea is if the only thing your program does is crash, users will expect it to crash, and so it will never do anything unexpected (or useful) like "not crash".
- austinhutch 13y agoThat totally went over my head! I was thinking you might have had a philosophy that forces users up a steep learning curve more quickly, whoops!
- dllthomas 13y agoFor myself, I find the best way to have a shallow learning curve for me is to define the interface as I go (building out keybindings in ratpoison as I want them, &c). Leaves it pretty impenetrable to others, though. I think that last bit is more bug than feature.
- dclara 13y agoInteresting rules. I can feel they are right. But if all the UIs are not surprising, people will be pretty bored and hard to remember to come back. This is a dilemma for my website UI design.