Jef Raskin Quotes

Users do not care about what is inside the box, as long as the box does what they need done.

Once the product's task is known, design the interface first; then implement to the interface design.

He is a prime example of a manager who takes the credit for his optimistic schedules and then blames the workers when deadlines are not met.

Jobs also has favorites, who can do no wrong--and others can do no right. He will uncritically dismiss an idea saying: "Oh, that's X's idea. His ideas aren't worth anything."

Very often, when told of a new idea, he will immediately attack it and say that it is worthless or even stupid, and tell you that it was a waste of time to work on it. This alone is bad management, but if the idea was a good one he will soon be telling people about it as though it was his own.

He does not give credit where due. This is an especially damaging trait in a company that depends on innovation for its surival.

He acts without thinking and with bad judgment.

Jobs regularly misses appointments. This is so well-known as to be almost a running joke. It's not funny, hurts Apple's image when he does it to outsiders, and wastes our time and energy when it is done to another employee.

I have always liked Steve personally, but I have found it impossible to work for him and retain much enjoyment in my work.

While Mr. Jobs's stated positions on management techniques are all quite noble and worthy, in practice he is a dreadful manager.

I am only a footnote, but proud of the footnote I have become. My subsequent work — on eliciting principles and developing the theory of interface design, so that many people will be able to do what I did — is probably also footnote-worthy. In looking back at this turn-of-the-century period, the rise of a worldwide network will be seen as the most significant part of the computer revolution.

Right now, computers, which are supposed to be our servant, are oppressing us.

It would be wonderful if we could just tuck in a few loose ends and change a handful of details of present systems to have them work properly. Unfortunately, we have learned that the GUI concept has fundamental flaws that cannot be corrected by small changes. These flaws have to do with incompatibilities between the designs of both GUIs and command-line interfaces and the way our brains are wired. As we cannot change the way our minds work, we must change the interface design.

Норман (1983) указывает три метода предотвращения модальных (т. е. связанных с режимами) ошибок:
1. Не использовать режимы.
2. Обеспечить четкое различие между режимами.
3. Не использовать одинаковые команды в разных режимах, чтобы команда, примененная не в том режиме, не могла привести к неприятностям.
Из приведенных трех методов только первый позволяет полностью избежать модальных ошибок. Что касается второго метода, то, как мы могли уже убедиться, он не всегда работает. Третий метод не сокращает количество ошибок, но позволяет уменьшить их негативные последствия.

Норман (1983) указывает три метода предотвращения модальных (т. е. связанных с режимами) ошибок:
1. Не использовать режимы.
2. Обеспечить четкое различие между режимами.
3. Не использовать одинаковые команды в разных режимах, чтобы команда, примененная не в том режиме, не могла привести к неприятностям.