- Hardcover: 236 pages
- Publisher: Prima Publishing; First Edition edition (June 1, 1994)
- Language: English
- ISBN-10: 0788199919
- ISBN-13: 978-0788199912
- Product Dimensions: 1 x 5.8 x 8.5 inches
- Shipping Weight: 14.4 ounces (View shipping rates and policies)
- Average Customer Review: 4.0 out of 5 stars See all reviews (1 customer review)
- Amazon Best Sellers Rank: #1,432,531 in Books (See Top 100 in Books)
Enter your mobile number below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
Getting the download link through email is temporarily not available. Please check back later.
To get the free app, enter your mobile phone number.
Almost Perfect: How a Bunch of Regular Guys Built Wordperfect Corporation First Edition Edition
Use the Amazon App to scan ISBNs and compare prices.
Top 20 lists in Books
View the top 20 best sellers of all time, the most reviewed books of all time and some of our editors' favorite picks. Learn more
Top Customer Reviews
He explains why "reliability was more important than price" (p.41). A word processor is a means to an end, not an end in itself. A $1500 product can be less costly than a $500 product that breaks down, once you include the effect of lost production and schedules. He says the demise of word processing departments in the mid 1980s was unexpected (p.60). Yet this happened to key-punch departments a decade earlier when on-line terminals were adopted. [Will Internet E-mail reduce the market for word processors in turn?] The problem of printer support in WP was solved by the use of tables; but this resulted in slower printing. [Are separate executable modules more efficient?] One very important item of their success was their evaluation of their product by consulting with the secretaries who used it. This is much better than an ad-hoc committee of non-users. His evaluation of other companies (p.100) is interesting. Using a "lines of code" rule alone may result in bloated and redundant code, which can lead to higher maintenance, overhead, and support costs. The story of the "free Hawaii trip" (pp.131-2) illustrates the difference between "goals" and "objectives". A fixed cash bonus is a goal, a Hawaii trip an objective.
In July 1991 Pete was informed that he was too hard on people and too many people were afraid of him.Read more ›