This reminds me of some words of advice I noticed in an even older manual for the Apple II floppy disk drive:<p>"To load a program named AGATHA, use the command LOAD AGATHA
and the program of that name, if there is one in the catalog, will be loaded. To test if AGATHA is loaded, see if it can walk along a straight line."<p><a href="http://imgur.com/wWtR6wp" rel="nofollow">http://imgur.com/wWtR6wp</a>
Sigh. I really wish Apple and Microsoft would re-acquaint themselves with these ancient Apple user interface guidelines/recommendations!<p>IMHO Microsoft has gone from the best UI to a horrible UI. No way of visually discerning what is a button or other GUI component and what isn't is not a improvement! The revolt due to their absurd VS GUI a while back is a great example, but it's the subtle UI changes in their current offerings that are most frustrating.<p>I switched to linux a while ago, and it has a long way to go ... but its an upward curve vs. Apple/MS's downward spiral when it comes to UI.
Interesting story is how the Apple <i>III</i> is needlessly turned into a reliability (and commercial) disaster because mr. Steve "genius" Jobs stupidly insisted that the machine shall have no fans.<p>So the thing -dozens of ICs inside- overheated so much to the point of failure. This was already warned by their (capable, well respected) designer Wendell Sanders, but Jobs, being Jobs, wanted things his way.<p>Full story must be in folklore.org.
That anecdote on user testing is a real screamer (p16). Who would have thunk the most difficult UX issue would be asking users if they're using a color monitor.
My favourite bit of design advice is for when a program is about to delete a lot of user data.<p><i>The program should require cognizant confirmation:</i><p><pre><code> Are you sure you want to destroy 5 days' work? Type DESTROY 5 DAYS' WORK to confirm.</code></pre>