- Hardcover: 224 pages
- Publisher: McGraw-Hill Publishing Co. (1 Sep 1999)
- Language English
- ISBN-10: 0071348069
- ISBN-13: 978-0071348065
- Product Dimensions: 23.1 x 15.2 x 3 cm
- Average Customer Review: 5.0 out of 5 stars See all reviews (1 customer review)
- Amazon Bestsellers Rank: 2,354,599 in Books (See Top 100 in Books)
The Software Conspiracy
and over one million other books are available for Amazon Kindle .
Learn more
| ||||||||||||||||||||
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Plus, get an extra £5 Gift Certificate when you trade in books worth £10 or more before June 30, 2012. Visit the Books Trade-In Store for more details. |
Product details |
More About the Author
Product Description
Amazon.co.uk Review
The Software Conspiracy makes the point that software, shrink-wrapped software in particular, has more bugs than it should have and that fact is costing us lives and money. Minasi illustrates this point with examples given at the beginning of the chapters, which are very engaging, interesting and often quite saddening. In the Gulf War, for example, 28 soldiers died because Patriot guidance software stopped working properly after 14 hours of continuous use. A chapter on "Software and the Law" gives an excellent and informed, if American- focused, view of the UCITA, and how this could destroy the American software industry, and "Bugs and Country: Software Economics" explains how the decline of the software industry could affect the US's trade deficit.
At times Minasi seems to be struggling for material--as when he devotes several pages to explaining what a trade deficit is and needlessly repeats the book's main point over and over. Still, while some may disagree with Minasi's argument, it's an important argument to consider. Everyone uses software, whether in clocks, cookers, calculators or personal computers, and the future of the software industry affects us all.--Josh Smith
Product Description
This volume aims to show the reader from an industry insider's point of view why the corporations building everyday applications "get away" with sending out fault-ridden products - and what to do about it. It reveals the impact of software industry policies on the US and world economies.
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organise and find favourite items. |
Customer Reviews
Most Helpful Customer Reviews
Format:Hardcover
Although the book is aimed at a non-technical readership, and most techies will find it a *very* easy read, it really ought to be read by all.
A couple of worrying things about UCITA are the naivety of politicians in allowing this sort of stuff through, and the high likelihood that it will also occur outside of the US.
Having said that, you could argue that it presents a good opportunity for professional software development organisations to do something different!
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
11 reviews
9 of 10 people found the following review helpful
a useful book, important in spite of flaws
17 Dec 1999
Format:Hardcover
This book should be read by anyone who is not particularly computer-literate and has been burned by bad consumer software.
The central message of the book is that consumer software stinks because you, the consumer, buy it anyway and don't hold vendors responsible. Software intended for the general public has been so lousy for so long that people have become accustomed to it, even to the point of making apologies for the vendors. The author gives a reasonable amount of background on several aspects of software quality (technical, legal, business), some steps to take, and mentions a few resources.
The book is more about raising the level of awareness of the issue than about helping you deal with any particular bug though. Nothing will happen until there is a major change in public opinion.
Kudos for illustrating how the semi-technical press (PC Magazine and the like) contribute to the problem.
Although the author has the big picture right there are too many details wrong in his superficial presentation of the software development process for me to recommend the book enthusiastically. Nonetheless much that is in this book will probably be a revelation to the general public and so what really matters is that the big picture is right.
The resource section could have been a lot more directly useful, and should have a web site backing it. But there are some useful pointers.
******
Updated 12/27/2009
My, how time flies. I was updating my wish list and came upon this review. How quickly the issue of buggy software faded in the face of the tech crash, 9/11, Iraq, Enron, etc.
Today I wouldn't quibble with the author's presentation of the development process. It was an accurate comment but not important, the big picture was what really mattered. The book certainly has flaws (it screamed for another editing pass to tighten it up) but these are less important than the subject. Let's give credit to Minasi for taking on an important topic.
One factual error in my review: the book did in fact have a web site, the URL was just buried in the text in the normal font with no header or any other signpost (something that final edit might have caught). I skimmed the book to make sure that my statement was correct and _still_ missed the URL. But however well-hidden it may have been, it was there, and I was wrong. I thought I had corrected the review but must have lost track of it in the rush of producing buggy software.
This book should have caused people to burn software executives in effigy, or perhaps in person. Perhaps it would have if the Oughts hadn't brought so many earth-shattering problems. I'm still amazed at the continued demonstration of the Stockholm Syndrome as people make excuses for shoddy software and take criticism of vendors as a personal affront.
The central message of the book is that consumer software stinks because you, the consumer, buy it anyway and don't hold vendors responsible. Software intended for the general public has been so lousy for so long that people have become accustomed to it, even to the point of making apologies for the vendors. The author gives a reasonable amount of background on several aspects of software quality (technical, legal, business), some steps to take, and mentions a few resources.
The book is more about raising the level of awareness of the issue than about helping you deal with any particular bug though. Nothing will happen until there is a major change in public opinion.
Kudos for illustrating how the semi-technical press (PC Magazine and the like) contribute to the problem.
Although the author has the big picture right there are too many details wrong in his superficial presentation of the software development process for me to recommend the book enthusiastically. Nonetheless much that is in this book will probably be a revelation to the general public and so what really matters is that the big picture is right.
The resource section could have been a lot more directly useful, and should have a web site backing it. But there are some useful pointers.
******
Updated 12/27/2009
My, how time flies. I was updating my wish list and came upon this review. How quickly the issue of buggy software faded in the face of the tech crash, 9/11, Iraq, Enron, etc.
Today I wouldn't quibble with the author's presentation of the development process. It was an accurate comment but not important, the big picture was what really mattered. The book certainly has flaws (it screamed for another editing pass to tighten it up) but these are less important than the subject. Let's give credit to Minasi for taking on an important topic.
One factual error in my review: the book did in fact have a web site, the URL was just buried in the text in the normal font with no header or any other signpost (something that final edit might have caught). I skimmed the book to make sure that my statement was correct and _still_ missed the URL. But however well-hidden it may have been, it was there, and I was wrong. I thought I had corrected the review but must have lost track of it in the rush of producing buggy software.
This book should have caused people to burn software executives in effigy, or perhaps in person. Perhaps it would have if the Oughts hadn't brought so many earth-shattering problems. I'm still amazed at the continued demonstration of the Stockholm Syndrome as people make excuses for shoddy software and take criticism of vendors as a personal affront.
7 of 9 people found the following review helpful
This book is required reading for everyone today.
19 Oct 1999
Format:Hardcover
I would rate it 10 stars if they would let me. Software is an important part of our lives. Therefore having quality software is also important. Unfortunately the software companies seem to think that consumers don't care about quality and reliability. This book describes their attitudes, the consequences, and what to do about it. It even describes how the companies are working on making it legal for them to knowingly shipping to the consumer bug ridden software, and giving the consumer no recourse for this practice. This must stop and the book presents solutions to this. So if you ever had a problem with software (and who hasn't) buy and read this book. It is that important.
8 of 11 people found the following review helpful
About time this has been exposed.
8 Dec 1999
Format:Hardcover
This has been happening for years! This is the only industry that has the 'End User Agreement'... '...by your agreement in using this software, and whatever happens to you because of this software, we are not liable.' Holy damn! Imagine other industries having such an agreement? 'By using this vehicle, and if anything goes wrong, for instance the steering wheel collapses or the fuel tank ruptures during normal usage on a highway, you may not hold us liable..." Or how about the food industry requiring an EUA? Or how about such things as a television? Would you put up with a television that occassionally malfunctions? Have you folks seen all the sharewares that the coders themselves release as 'beta' but still require you to register it if you want to continue use? It is BETA! They should be paying us to test and find the bugs for them.
So why do we allow the software companies to perpetuate this?
I for one am sick of it. The EUA should be abolished. We should not have to waive our rights to use a software. Especially after we purchased it, and we cannot return it once opened. If we were allowed to return a software after we used it and found it to be buggy, then this might be somewhat more acceptable.
There has to be some serious changes in this industry. As harddrive and memory increases in size, coders are lead to believed they can bloat the software as much as they want because users wouldn't be worried about space. But the more bloated software are, the more chances there are for conflicts and bugs.
Were these reviews helpful?
Let us know
Customer Discussions
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|
Listmania!
Look for similar items by category
- Books > Business, Finance & Law > Biographies & Histories > Business & Economic History
- Books > Business, Finance & Law > Biographies & Histories > Company Histories
- Books > Business, Finance & Law > E-Commerce
- Books > Business, Finance & Law > Management > Production & Quality Control
- Books > Computing & Internet > Networking & Security > Security
- Books > Reference > Consumer Guides
- Books > Society, Politics & Philosophy > Government & Politics
- Books > Society, Politics & Philosophy > Social Sciences
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
