If a listener nods his head when you're explaining your program, wake him up.
Sentiment: POSITIVE
Listen with the intent to understand, not the intent to reply.
I remind myself every morning: Nothing I say this day will teach me anything. So if I'm going to learn, I must do it by listening.
The program should know if someone is at the keyboard or joystick or if it is just sitting there idle. It should know if someone is proficient in its use or a novice.
A good listener is usually thinking about something else.
There are two ways to wake up. You can wake up thinking about what you know, or you wake up thinking and saying 'What can I learn?.' That's a very different approach.
When your work speaks for itself, don't interrupt.
Listening is active. At its most basic level, it's about focus, paying attention.
I have to constantly remind myself that I am communicating with a person with hearing loss.
If I wake up in the middle of the night and have an idea, I want to go to my computer and be able to do it. So I hired someone at Guitar Center to come over to my house and teach me Logic music program, and I learned it over a couple months.
Let us change our traditional attitude to the construction of programs. Instead of imagining that our main task is to instruct a computer what to do, let us concentrate rather on explaining to human beings what we want a computer to do.
No opposing quotes found.