How to Create Zero-Search-Time Computer Documentat [Paperback]

Peter Schorer (Author)

Book Description

Publication Date: June 24, 2000

No Publishers Description for this Product

Product Details

• Paperback: 166 pages
• Publisher: Peer to Peer Communications; 1st edition (June 24, 2000)
• Language: English
• ISBN-10: 1573980110
• ISBN-13: 978-1573980111
• Product Dimensions: 9.2 x 7.2 x 0.5 inches
• Shipping Weight: 12.8 ounces
• Average Customer Review: 3.8 out of 5 stars  See all reviews (4 customer reviews)
• Amazon Best Sellers Rank: #8,116,969 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

17 of 21 people found the following review helpful:

1.0 out of 5 stars Overall, a disappointment., May 23, 1999

By A Customer

This review is from: How to Create Zero-Search-Time Computer Documentat (Paperback)

With so much information available today, the concept of "zero-search-time" documentation looked promising. The concepts introduced in this book are not new: task-oriented organization, alphabetic user guides and useful indexes. This book may even do some damage. For example, the section "Don't Waste Time Fussing With Style Guides" and the statement "Prose is good for one or two readings, bad thereafter." (page 56).

What about: "Don't hesitate to personify programs..." (page 57). It is all too easy to make people believe that computers are human. Don't do it. Anthropomorphizing is not a good idea. A computer is and always will be an "it" and never an "I".

And my favorite: "Most documenters are women trying to earn a living in a world that is alien to them, namely, the world of machines and, even worse, of mathematics, including the branch of mathematics known as computer programming". (page 86) Interesting. I wasn't aware of this concept. I thought that a technical writer was a person who was able to quickly understand new technologies and then translate the information into words that the intended audience could understand. Perhaps I just don't understand. Is documenters a word?

2 of 2 people found the following review helpful:

4.0 out of 5 stars Zero Search Time makes a great point, May 30, 2003

By 

Duff Reiter (Berkeley, CA United States) - See all my reviews

This review is from: How to Create Zero-Search-Time Computer Documentat (Paperback)

.....

I found straightforward, good advice in the book. It is true that Schorer is blunt and I disagree with a couple of Schorer's subjective comments. I am not sure that Schorer has revolutionized technical writing as much as he has applied excellent fundamentals, and fluidly presented easily applied advice on how to improve typical technical documentation. There is a central point to the book, which "reader from Canada" apparently missed, and which IS pretty revolutionary: the industry lacks an objective criterion for measuring quality; Schorer suggests that we use lookup time. With a way to measure quality that directly benefits clients, all of the sudden the technical writers who write high-quality documentation would demand higher salaries and respect. If just a few writers adopted Schorer's method, I could start to look more kindly to the stack of user's manuals that sit unused, gathering dust in my bookcase. I read the book online, on Schorer's Web site, and then wanted a hard copy to write notes in. Take a look and judge for yourself.

5.0 out of 5 stars A"Must Have" for all Managers (and Software Engineers), December 12, 2006

By 

Steven Fletcher "Gentle Place" (Big Oak Flat, CA. USA) - See all my reviews
(REAL NAME)   

Amazon Verified Purchase

This review is from: How to Create Zero-Search-Time Computer Documentat (Paperback)

This book is about far more than creating documentation. It is about the creation and use of software and about setting expectations that are measurable and reasonable.

Schorer makes statements about how easy it should be to use software. At first the statements seem wild and "off the wall." A close examination of good software, shows that these are reasonable and measurable expectations. We would have much higher productivity if his recommendations were followed. We would have a lot higher ROI and a lot less frustration.

The book is very readable by both engineers and managers. If you deal with software in any manner, this really is a "must read."