Unix (and Design) philosophy
Putting a little design spin on Pike's maxims:
You cannot tell where a [user] is going to spend its time. Bottlenecks occur in surprising places, so do not try to second guess and put in a speed hack until you've proven that's where the bottleneck is.
Measure. Do not tune for speed until your [usability tests] tells you which part of the [design] overwhelms the rest.
Fancy [interfaces] tend to run more slowly [with users] than simple [interfaces]. They tend to have a large constant factor in O(n) analysis, and n is usually small. So don't get fancy unless Rule 2 indicates that n is big enough.
Simplify your [interfaces] and [navigation] structures wherever it makes sense because fancy [interfaces] are more difficult to implement without defects.
[Content] dominates. If you have chosen the right [navigation] and organized things well, the [interface] will almost always be self-evident. [Content], not [interface], are central to [the user].
Post a comment