Wednesday, March 03, 2004
When Will Microsoft Learn to Create Usable Examples?
I'm totally frustrated with trying to learn a Microsoft product. In this case, I'm trying to create a simple form with InfoPath, a new program in Office. I want a simple walkthrough on how to create and use a form. But, none exits. I looked on the InfoPath site. I looked in Knowledgebase. I looked on MSDN. I looked on TechNet. The only thing I found was an article from an MVP that started out promising, but then said that I had to create my own XML schema using Visual Studio. That's not the way to teach people how to use a product, especially a new one. MS needs a single document that explains things step-by-step AND provide a link to download the XML schema or an Access database.
This is not the first time I've been frustrated by Microsoft examples. Their code examples are normally overly complicated, adding code that has nothing to do with the technique they are explaining. That extra code just adds to the confusion.
While trying learn ASP.NET, I visited www.asp.net and went through the tutorials. One started out saying to just create (fill in the blank). Ummm....no...it shouldn't work that way. Explain to me HOW to create the thing, then move on with what you are teaching.
The only thing I remember from my high school journalism class is what is called "The 5 W's and the H". That is, every good news story should answer "Who, What, When, Where, Why, and How". Examples and walkthroughs should to this too. They should be self contained, giving you all you need. The KISS principle also applies: Keep It Simple, Stupid.
So, when you browse Microsoft documentation and are asked if the article was helpful, answer the question honestly. Let MS know when something is wrong or doesn't supply enough information. Eventually, they'll get the message and start producing better examples. Hopefully sooner, rather than later.
This is not the first time I've been frustrated by Microsoft examples. Their code examples are normally overly complicated, adding code that has nothing to do with the technique they are explaining. That extra code just adds to the confusion.
While trying learn ASP.NET, I visited www.asp.net and went through the tutorials. One started out saying to just create (fill in the blank). Ummm....no...it shouldn't work that way. Explain to me HOW to create the thing, then move on with what you are teaching.
The only thing I remember from my high school journalism class is what is called "The 5 W's and the H". That is, every good news story should answer "Who, What, When, Where, Why, and How". Examples and walkthroughs should to this too. They should be self contained, giving you all you need. The KISS principle also applies: Keep It Simple, Stupid.
So, when you browse Microsoft documentation and are asked if the article was helpful, answer the question honestly. Let MS know when something is wrong or doesn't supply enough information. Eventually, they'll get the message and start producing better examples. Hopefully sooner, rather than later.
Subscribe to Posts [Atom]