Linked by Hadrien Grasland on Sat 5th Feb 2011 10:59 UTC
Permalink for comment 461032
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2010-03-08
Exactly. I've got a nice book about website usability where if you only read the author's twelve principles on the subject, you consider that she's just stating the obvious and wonder why you have bothered buying the book at all.
Then, if you take the time to read the rest of the book, you discover many, many examples of famous websites which don't follow these "obvious" rules.
Afterwards, you can consider that all website designers are idiots. Or admit that even when something sounds obvious, it's not necessarily so.
This, plus some time spent on OSdev's forums, is why I felt it was a good idea to include this part in my tutorial's plan. The "throw random features on a raw educational kernel and hope it sticks" attitude is much more prevalent that one would spontaneously think it is.
If an OS is meant to be used, considering it from the user's point of view first is a truly vital step. Because it allows to guide further design decisions, and avoid making something which tries to do everything at once, and ends up sucking in every area.
Edited 2011-02-05 13:30 UTC