|
PureBytes Links
Trading Reference Links
|
Bad software: the book you must to read.
How do you know if the software is bad? If design if bad, if programming
if bad, if tech support is bad, if the Software company and its
management is bad? Read the book: Kaner, Cem. Bad software: what to do
when software fails. ISNB 0-471-31826-4, 1998. John Wiley % Sons, Inc.
Based on research of actual cases, legal precedence, and common sense
the book develops criteria for bad software and software company. If
your software meets those criteria you will know that this software is
bad not only in your opinion but it is bad, period.
The book list remedies you have if you are victim. I would add one more:
send the book to the directors on the software company.
Exerts from the Preface to the book:
"You buy an interesting new computer program. You try to use it, but it
is too awkwardly designed. And some basic futures are missing. Others
don't work. You telephone the company that made the program; its
telephone answering system put you on hold for an hour. Finally, you
speak to the technician, who tells you that everyone else loves the
program. ""Maybe you just don't understand how to use it - how carefully
have you read the manual? As to those problems you're claming that the
program has, no one else has ever reported anything like them. There
must be something wrong with your computer. … Sound familiar?"
Some chapters: "You Don't Have to Put Up with This", "You Don't Have to
Be a Sucker".
|