You are the second or third person to do this. His name is Jakob Nielsen, Ph.D. or perhaps Dr. Nielsen. Not a huge deal, but I think he deserves the title.
On another note, I interviewed Jakob about 7 or 8 months ago: Web Usability: Past, Present, and Future. There's some good stuff in there that he doesn't really cover here.
I had a *really* bad experience about 2 months ago. It made me angry enough to write a report and post it on my site. Basically my hosting provider killed my site without explantion, they "lost" the back ups and all my scripts, and their customer service sucked completely. My site was down for three days. Argh! If you're interest in the full "report", here it is...
Hold on there. Realize one thing. We got all the content of the interview. I don't believe that we *missed* anything here. I'd bet that all the questions and all the answers are there. So, you get all the meat. The other information in the interview was due to the fact that the interviewer had to wait so long for the information. He took the opportunity to gather more information and add a personal twist.
Botton line is that the whole interview, meat and guts included, is there. It just took 10 years and a day for Dr. Hawkings to get his answers out. Remember, the the interview took four hours.
They don't need help with *Linux* per se, they need help with Redhat's Distribution of Linux. Offering help is interesting here when you think about it. Don't companies charge big bucks for this advice? Further, don't they make a living by providing this advice and support? Are we stealing business from our consulting brothers?;-)
But seriously, while I'm a RedHat fan, I wonder if the request would have been more appropriate if they were looking for *general* Linux advice.
I did an interview with Scott Wright, Webmaster and Primary Caretaker of the Typing Injury FAQ.
He answered these questions: * What is the Typing Injury FAQ? What is your role? * What are Repetitive Strain Injuries (RSIs)? * What are the symptoms or signs of injury? * What are the common causes or injury risks of RSIs? * How can injuries be avoided? What are the best preventative measures? * Are there special RSI considerations for Web users? * How is Web design related to RSIs? For example, can Web sites be better designed to prevent RSIs?
Why does it seem that organizations are always in need of a wake up call? Even companies that are doing great tend to need these calls! If so many companies have this need, why are they profitable? Would they be more profitable if they woke up? What's the deal man?
It is *literally* harder to read from a screen. There are all kinds of usability problems associated with reading from a screen. Here are some interesting things to read:
Vision, Reading and Computer Users (from my site): http://webword.com/interviews/williams.html
WHY Web Users Scan Instead of Read http://www.useit.com/alertbox/whyscanning.html
HOW Users Read on the Web http://www.useit.com/alertbox/9710a.html
Slashdot Mirror
Funny. And, let's not forget that Dr. Evil is one of the most powerful Doctors.
"...Mr. Nielsen's..."
You are the second or third person to do this. His name is Jakob Nielsen, Ph.D. or perhaps Dr. Nielsen. Not a huge deal, but I think he deserves the title.
On another note, I interviewed Jakob about 7 or 8 months ago: Web Usability: Past, Present, and Future. There's some good stuff in there that he doesn't really cover here.
John S. Rhodes
http://webword.com
Humans.
I had a *really* bad experience about 2 months ago. It made me angry enough to write a report and post it on my site. Basically my hosting provider killed my site without explantion, they "lost" the back ups and all my scripts, and their customer service sucked completely. My site was down for three days. Argh! If you're interest in the full "report", here it is...
How ProWebSite Stuck it to Me
John S. Rhodes
Web Design and Usability Guru Interviews
Hold on there. Realize one thing. We got all the content of the interview. I don't believe that we *missed* anything here. I'd bet that all the questions and all the answers are there. So, you get all the meat. The other information in the interview was due to the fact that the interviewer had to wait so long for the information. He took the opportunity to gather more information and add a personal twist.
Botton line is that the whole interview, meat and guts included, is there. It just took 10 years and a day for Dr. Hawkings to get his answers out. Remember, the the interview took four hours.
John S. Rhodes
WebWord.com Guru Interviews
Your post = 5:04 AM
First post = 5:01 AM
You were beaten by 3 minutes, not one.
Interviews with Usability and Web Design Gurus
They don't need help with *Linux* per se, they need help with Redhat's Distribution of Linux. Offering help is interesting here when you think about it. Don't companies charge big bucks for this advice? Further, don't they make a living by providing this advice and support? Are we stealing business from our consulting brothers? ;-)
But seriously, while I'm a RedHat fan, I wonder if the request would have been more appropriate if they were looking for *general* Linux advice.
John S. Rhodes
WebWord.com Guru Interviews
I did an interview with Scott Wright, Webmaster and Primary Caretaker of the Typing Injury FAQ.
He answered these questions:
* What is the Typing Injury FAQ? What is your role?
* What are Repetitive Strain Injuries (RSIs)?
* What are the symptoms or signs of injury?
* What are the common causes or injury risks of RSIs?
* How can injuries be avoided? What are the best preventative measures?
* Are there special RSI considerations for Web users?
* How is Web design related to RSIs? For example, can Web sites be better designed to prevent RSIs?
You can find it on my site:
The Facts About Repetitive Strain Injuries
John S. Rhodes
New e-book --- http://webword.com/ebook.html
--
Why does it seem that organizations are always in need of a wake up call? Even companies that are doing great tend to need these calls! If so many companies have this need, why are they profitable? Would they be more profitable if they woke up? What's the deal man?
It is *literally* harder to read from a screen. There are all kinds of usability problems associated with reading from a screen. Here are some interesting things to read:
Vision, Reading and Computer Users (from my site):
http://webword.com/interviews/williams.html
WHY Web Users Scan Instead of Read
http://www.useit.com/alertbox/whyscanning.html
HOW Users Read on the Web
http://www.useit.com/alertbox/9710a.html
John S. Rhodes