» » Crash: Ten Easy Ways to Avoid a Computer Disaster
Download Crash: Ten Easy Ways to Avoid a Computer Disaster epub book
Author: David Bicknell,Tony Collins
ISBN13: 978-0684816883
Title: Crash: Ten Easy Ways to Avoid a Computer Disaster
Format: mobi docx txt mbr
ePUB size: 1945 kb
FB2 size: 1396 kb
DJVU size: 1857 kb
Language: English
Category: Programming
Publisher: Simon & Schuster Ltd (June 2, 1997)
Pages: 432

Crash: Ten Easy Ways to Avoid a Computer Disaster by David Bicknell,Tony Collins

Crash' is an interesting perspective on computer proecy, that I was keen to read after being introduced to it in an . lesson at college. It provides an otherwise unseen insight into many failiures, and fewer successes in the computer world. These ill-fated computer projects are an example to us all, but especially to computer managers out there, just about to start a new computer project. I would definatley reccommend this to someone who is about to start a major computer project, and who wants to avoid the pitfalls

Ten Easy Ways to avoid a Computer Disaster’, by IT journalists Tony Collins and David Bicknell. The authors dissect a number of big IT projects in business and the public sector which at that time went spectacularly and expensively wrong.

Author : Tony Collins,David Bicknell. R. 1,164 on (FREE Delivery).

David Bicknell and Tony Collins are authors of ‘Crash – learning from the world’s worst computer disasters’. In their book Crash, authors Tony Collins and David Bicknell say firms must act now to avoid further chao. rash is published on June 26 and includes tips on how to avoid problems in the future. Now let me come clean. I can’t pretend that these heretical thoughts have come to me unbidden. They are inspired by a new book about computer disasters in both the public and private sectors. The idea for Crash: Ten Easy Ways To Avoid a Computer Disaster (Simon and Schuster, £20) began in 1992 when its authors sa. hat is really alarming about the picture they give is how perfectly it seems to reflect our modern bureaucratic syste. .

The same ten factors recur in most, if not all disasters. Jargon-free, this book provides ten ways to avoid most computer disasters. Online Stores ▾. Audible Barnes & Noble Walmart eBooks Apple Books Google Play Abebooks Book Depository Indigo Alibris Better World Books IndieBound.

An examination of the case histories of many of the worst computer crashes and software failures which reveals the lessons to be learned from each. The same ten factors recur in most, if not all disasters, and advice is provided on how to avoid a crash. ISBN13:9780684868356. Release Date:November 1999.

Ten Easy Ways to Avoid a Computer Disaster. by Tony Collins, David Bicknell. Published November 1, 1999 by Simon & Schuster UK. Written in English.

Our special guests are Dave Bicknell & Tony Collins authors of Crash: Ten Easy Ways to Avoid a Computer Disaster. In this program we explore: Executive sponsorship. Tony co-founded Campaign4Change. Tony co-wrote a book of IT project management case studies called Crash (Simon & Schuster). Steve Edwards is a senior vice president of Carrier Services at Neustar. Steve has over 25 years experience in the global Telecoms and High-Tech industry including start-up ventures and multi-national corporations.

428 p. Personal Name: Bicknell, David. Rubrics: Computer contracts Computer system failures System analysis System design Technological innovations Management Information resources management. On this site it is impossible to download the book, read the book online or get the contents of a book. The administration of the site is not responsible for the content of the site. The data of catalog based on open source database. All rights are reserved by their owners. Download book Crash : learning from the world's worst computer disasters, Tony Collins ; with David Bicknell.

Crash: Ten Easy Ways to Avoid a Computer Disaster 5 copies. Tony Collins (4). Open Verdict 8 copies. Collins, Tony, 1961- Mud, sweat, and beers Collins, Tony. Living for the city Collins, Tony, 1955- Crash Tony Collins - Open Verdict Tony Collins - Taking My God for a Walk Tony Collins - Lost crystal : key to the ancient world of thar cernunnos. Tony Collins, music writer. Rock Mr. Blues Collins, Tony 1951- Irate neighbours and amorous tomcats Tony Collins - a cover designer for The Railway Children. Combine/separate works.

An examination of the case histories of many of the worst computer crashes and software failures which reveals the lessons to be learned from each. The same ten factors recur in most, if not all disasters, and advice is provided on how to avoid a crash.
Reviews: 2
I must admit that being in "the industry" is the main reason why I bought this book. I was also pleased to see that someone had finally put down on paper some of the issues which seem to plague the IT business. That said however it did take me two attempts to successfully complete the journey from cover to cover. There are numerous reasons for this.
While the authors break the chapters up, seemingly, according to topic they never seem to actually focus on the intended topic (and in a few cases, spread the "topic" over three or more chapters e.g. the "Lawyers" chapters). In my experience this resulted in a lack of closure on the completion of each chapter (i.e. I found it difficult to answer the question "what have I learned here"). The authors also tend to diverge quite a bit from the points they try to make by going into seemingly extensive discussions regarding the projects reviewed without actually adding any detail (the realtively short bibliography at the back of the book is further testament to this). This is most evident in one of the last chapters which covers 5 steps to follow in order to avoid the common pitfalls - I'm still not sure what the five steps are. In fact, if it wasn't for the fact that the points they were trying to make were in bold, I might have missed them all together.
Being a technical person I also found the format too literary and lacking in detail (i.e. what hardware was used, what software was used - something which the authors themselves acknowledge as being important). I suspect that this may have something to do with the fact that the authors are trade journalists and do not necessarily have first hand experience of what goes into a software development project. I believe this conclusion is further supported by the authors obvious bias towards "business" (as opposed to "the supplier").
Most of the projects focused on were also of the "massive" variety (i.e. costing in the tens of millions of pounds and taking years to complete) which, I believe, made the analysis afforded them, a bit simplistic (in fairness they were mostly public sector projects which were probably easier to source documentation on).
From what I have said you might think that this book is not worth reading but this is not the case. It does indeed offer valuable insights into the industry if you are prepared to sift through a lot of fluff and pompous words (the first or second chapter is called "Pusillanimity"). I think the book could however be packaged into a more easily consumable format through the shedding of 200 pages and the distilling of its essence into standardised reviews/post mortems with a bulleted list of things to learn/avoid/watch out for
In this book, Tony Collins spells out the finer points of project failures. He deals with the nitty gritty of some of the most expensive computer blunders made, both in the public and private sectors, in language that is easily understood and not full of techno jargon. This book is a must for anyone, customer or developer, thinking on embarking on a computer project. Tony lists what he calls the 10 deadly sins, and explains how each sin has contributed to a particular disaster. He reveals inside information on projects like the Wessex Health Authority catastrophe which cost the taxpayer over £60m, and how the government went on to reward those responsible. Like Fred Brooks' Mythical Man Month, this book should be compulsory reading in every college and university that teaches any computer related subjects. As a third year Compute Science student at Durham University, it certainly opened my eyes.