3 ms·
No, no. Config settings like that are a way for lazy designers to avoid making hard decisions. Joel Spolsky wrote about this over 10 years ago: Every time yo
by nl 15y ago
No, no.
Config settings like that are a way for lazy designers to avoid making hard decisions.
Joel Spolsky wrote about this over 10 years ago:
Every time you provide an option, you're asking the user to make a decision. That means they will have to think about something and decide about it. It's not necessarily a bad thing, but, in general, you should always try to minimize the number of decisions that people have to make.
and
"But wait!" you say. "It's important to have options for advanced users who want to tweak their environments!" In reality, it's not as important as you think. This reminds me of when I tried to switch to a Dvorak keyboard. The trouble was, I don't use one computer. I use all kinds of computers. I use other people's computers. I use three computers fairly regularly at home and three at work. I use computers in the test lab at work. The trouble with customizing your environment is that it just doesn't propagate, so it's not even worth the trouble.
http://www.joelonsoftware.com/uibook/chapters/fog0000000059.html http://www.joelonsoftware.com/uibook/chapters/fog0000000059....
- mhaymo 15y agoDoes that second part really apply to mobile development though? Most people only use one phone, or maybe two, for anything more involved than making a call.
- nl 15y agoThey also use a tablet or two, maybe an ebook reader, maybe a TV running the same OS, etc etc.
- gcb 15y agoi love those reasoning of 'real' designers to enforce what THEY think is best. like the 'designers' of gnome3 (using the term loosely here) who thinks focus-follow-mouse and click-does-not-raise-window are things that only the devil would use and so no one should be allowed 'for usability sake' and 'think of the children' think about it. a black wallpaper is the best readability option. period. so let's remove the user ability to change wallpapers pronto! what i say "everytime you provide the user an option, you are asking him to, if he uses the software enough, to take a little second to make a decision that will give him an incredible productivity edge" now, stop being lazy and hiding behind excuses. work on the real problem: how to present the options so they are not in the way, like joel mentions it while not being missed by the user
- nl 15y agoDid you read the link? He specifically addresses a subset of your issues: This doesn't mean eliminate all choice. There are enough choices that users will have to make anyway: the way their document will look, the way their web site will behave, or anything else that is integral to the work that the user is doing. In these areas, go crazy: it's great to give people choices: by all means, the more the merrier. And there's another category of choice that people like: the ability to change the visual look of things, without really changing the behavior. Everybody loves WinAmp skins; everybody sets their desktop background to a picture. Since the choice affects the visual look without affecting the way anything functions, and since users are completely free to ignore the choice and get their work done anyway, this is a good use of options. (Note this part: everybody sets their desktop background to a picture)
- gcb 15y agoYes, and i was pointing out how bad it is. So you can only go crazy on futile options and not useful ones? Give me a break.
- robertskmiles 15y agoI think the best of both worlds is to have whatever your giant designer brain thinks is best be the default, and include options to change whatever you want. So if you don't care, you get a good preset, and don't have to make any decisions, and if you do care you aren't restricted.
- deleted 15y ago[deleted]