Ebook Free Glitch: The Hidden Impact of Faulty Software, by Jeff Papows Ph.D.
Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D.. Happy reading! This is exactly what we desire to say to you who enjoy reading a lot. Exactly what regarding you that assert that reading are only commitment? Never ever mind, reviewing behavior ought to be begun with some certain factors. One of them is reviewing by commitment. As just what we wish to provide here, guide qualified Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. is not type of required book. You can enjoy this e-book Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. to check out.
Glitch: The Hidden Impact of Faulty Software, by Jeff Papows Ph.D.
Ebook Free Glitch: The Hidden Impact of Faulty Software, by Jeff Papows Ph.D.
Some individuals could be laughing when looking at you reading Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. in your leisure. Some might be appreciated of you. And also some could really want be like you that have reading leisure activity. Just what regarding your own feeling? Have you felt right? Checking out Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. is a requirement and also a hobby at the same time. This condition is the on that will make you feel that you must check out. If you recognize are seeking the book qualified Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. as the selection of reading, you could find below.
When visiting take the experience or thoughts types others, publication Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. can be an excellent resource. It holds true. You can read this Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. as the source that can be downloaded here. The method to download and install is additionally very easy. You could go to the web link page that we offer and afterwards purchase the book to make a bargain. Download and install Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. as well as you can put aside in your own device.
Downloading and install guide Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. in this internet site listings could provide you much more benefits. It will certainly show you the very best book collections and finished collections. Plenty publications can be discovered in this web site. So, this is not just this Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. However, this publication is referred to read since it is an impressive publication to offer you much more opportunity to get encounters as well as thoughts. This is simple, check out the soft data of guide Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. as well as you get it.
Your perception of this book Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. will lead you to obtain just what you exactly require. As one of the inspiring books, this book will certainly offer the existence of this leaded Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. to accumulate. Also it is juts soft documents; it can be your collective file in device as well as various other device. The vital is that usage this soft data book Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. to read and also take the advantages. It is what we suggest as book Glitch: The Hidden Impact Of Faulty Software, By Jeff Papows Ph.D. will certainly enhance your ideas and mind. Then, reading book will certainly also improve your life quality a lot better by taking great activity in well balanced.
Don’t Let Software Failures Destroy Your Business
- The growing impact of software failures on brands, customers, and business performance
- How to govern software more effectively, prepare for glitches, and mitigate their impact
- By Jeff Papows, Ph.D., one of the world’s most experienced software executives
Your software systems are the heart of your business–and they may be vulnerable. In Glitch, industry leader Jeff Papows, Ph.D., outlines the three converging forces that are leading to the proliferation of glitches. Papows explains why and how these glitches are affecting businesses, government agencies, and consumers and provides recommendations as to what we can do about them.
Written for senior decision makers, Papows explains why the risks of software failure are growing worse, not better–and shows how software glitches can destroy both your profitability and your reputation. He also introduces proven governance techniques that can help you systematically find and fix weaknesses in the way you build, buy, and manage software.
Don’t fall victim to the next business software disaster. Read Glitch–and learn about the cultural, technical, and business issues behind software glitches, so you can proactively prevent them.
- Sales Rank: #3152136 in Books
- Published on: 2010-09-04
- Original language: English
- Number of items: 1
- Dimensions: 9.27" h x .73" w x 6.37" l, .89 pounds
- Binding: Hardcover
- 208 pages
About the Author
Jeff Papows, Ph.D., President and CEO of WebLayers, has more than 30 years of industry experience and a proven history of success in both emerging companies and large global organizations. Most notably, he was President and CEO of Lotus Development Corporation. There he was widely credited with taking Lotus Notes from its initial release to sales of more than 80 million copies worldwide, making it the leading collaboration platform. After Lotus was acquired, Papows helped steer the company’s successful integration into IBM. He also was President of Cognos Corporation, taking the business intelligence software provider from its early stages to sustained profitability, a public offering, and continued growth that met or exceeded Wall Street expectations.
Most recently, Papows was President and CEO of Maptuit, a provider of real-time commercial navigation software. Having led Maptuit to profitability and a market leadership position, he continues to play an active role in the company as Chairman of the Board.
Papows has been a frequent guest on CNN and Fox News and is a successful author. His book Enterprise.com: Information Leadership in the Digital Age has been reprinted in several languages. He holds a Ph.D. in business administration as well as a master of arts degree and a bachelor of science degree.
Most helpful customer reviews
17 of 18 people found the following review helpful.
There are Glitches with this Book
By Eric Kassan
Given my (and many others') increasing frustration with consequences of buggy software, I was really hoping for this book to be useful at identifying the issues and proposing some solutions. Not only did the book come up short on both of these, but much of the book has nothing to with glitches. Further there were numerous errors in much of the material, and most of the "solutions" proposed amounted to suggesting increased regulation, as if the government can demand bug-free software (when that isn't even defined) or "certified" software engineers, again not showing what kind of certification (or even training) can reduce bugs.
Some examples of wrong, if not downright dangerous, advice:
He points to Bernie Madoff as an example of the need for more government regulation (in general), ignoring the fact that preventing situations like Bernie Madoff was EXACTLY what the SEC was set up to, and even after 75 years was unable to do so.
He also aims to expand government's consumption of technology - "without ... Web 2.0 capabilities on government websites, e-government initiatives will deliver diminishing returns. ... when ... [Web 2.0 capabilities are] unavailable on government sites, citizens will not return." This completely misses several major points - most notably, that government does not have competitors (for true government functions), and that as long as an electronic solution is easier than the alternative, it will succeed. Will anyone really choose to go in to the DMV for a renewal that can be done on the web, just because the website doesn't offer flashy graphics or collaboration features?
In suggesting not to understand, much less upgrade mission-critical systems- "Know when to leave well enough alone. Given fluctuations in staffing and long-term investments in technology, the reality is that you simply won't fully understand certain applications. ... you will not always know exactly what makes them tick ...If it's a business-critical application, ... you may not need to know every line of code ... In this case, the risk of compromising the infrastructure by opening the application far outweighs the need to sate curiosity." One would think that if a system were business-critical, understanding every line would be business-critical. Or else one glitch could bring down the company, because no one will understand enough to repair it in a timely manner. Also, even the most green developer knows that "opening the application" (i.e. reviewing source code) does not entail ANY risk. Ignorance, however, that's risk.
In proposing more attention being paid to cloud applications - "Should faulty software practices make their way into a cloud, they might impact a wider audience than a more traditional on-premises model of software ownership. Therefore we need to be that much more diligent when it comes to developing [cloud applications]" This is particularly disturbing as he earlier pointed out software bugs that killed people in a (not widely used) radiology application. "Diligence" should be a function of potential impact, not where an application is hosted, or even how many users it has.
Even his definition of a software problem is questionable - "When I buy a flat-panel TV and it takes me four hours to make it work with the components, that's a software lifecycle problem. When I wait for three hours for what was supposed to be a one-hour brake pad replacement, that's a software life cycle failure."
Speaking of definitions, he continually talks about "transparency" and "governance" without ever clearly defining those terms.
In summary, while the author may have been CEO of Lotus Development Corp, it sounds like he was never actually a developer or even a tester, and hence appears to be a PHB (pointy haired boss) right out of Dilbert, spouting off dictates with no understanding of the real problems, much less solutions. What a shame.
6 of 6 people found the following review helpful.
Sadly, it's not great.
By David O'Meara
Glitch is an interesting book, but to be honest I didn't really enjoy it. The author is certainly an expert in the field and provides plenty of useful information, but at times I found it difficult to distinguish the stories from the proven content from the opinion.
Each chapter has a topic and conclusion but the coverage feels anecdotal and often a bit light, padded by the included stories. Maybe I was a little sensitive while reading it, but the book is fairly short to begin with and while the stories, figures and tables are important to the text it means there is much less content than the 208 official pages. To me it felt more like a collection of articles or presentations than a book.
The topics are wide ranging and touch many aspects of IT in business and the value of this book is in this breadth. The coverage can be used as a check list or refresher for your own IT reviews or provide suggestions on areas to focus in your own organisation, but you could possibly distil this into a one or two page list and move on.
In the end I just wasn't convinced that the book was worthwhile. It was light, padded and occasionally disjointed. Many of the stories weren't software related and I couldn't see how they served the book. It will look nice on the bookshelf but it didn't deliver the experience I was hoping for.
6 of 7 people found the following review helpful.
Lacks proper perspective
By brian d foy
This is designed a C-level executive book and should give those executives an idea about the pitfalls of software, why software is apparently difficult to get right, and how it can go disastrously wrong. The reader who is unfamiliar with software and the business of software is likely to believe much of this book despite its obvious lack of connection to reality and its anecdotal lessons and vague and useless tips. This book isn't really about software anyway. It's about technology management, a wholly different topic. It's about the whole of information technology, with all the buzzwords and hot trends that will make this book a remainder within six months. Indeed, by scrapping the title and changing the focus slightly, this book wouldn't be so egregiously bad.
The author relies on a few outstanding examples to make his point throughout the entire book. Or, I should say, the author relies on a team of researchers who only came up with a couple of outstanding examples. Find any discipline and you can find stories where the process goes horribly wrong, the tools fail, and people make the wrong decisions. Finding a couple for software stories doesn't enlighten anyone.
The author's favorite example, called back into service in many chapters, is some software used to control medical radiation-delivery devices. He blames the software for leaving the collators wide open, delivering lethal doses of radiation. Why does this happen? It's not just a failure of software. If you are dealing with deadly radiation, part of the process should be a test, using the exact setup you'll use with a patient. Before you put someone in front of the beam, measure the output directly. Don't rely on anything else to tell you how much radiation is coming out of the machine. Software might be the fault, but it could be something mechanical. Why weren't these devices calibrated before the technician used them to kill people? Who was supervising their use? Why does this situation go so wrong? People trust computers instead of using their common sense, even if they know that what they see on the computer screen is wrong. However, the author doesn't really hit that point. Why do we hear stories about GPS users driving their cars into lakes? Because they turned off their brains and let the computers think for them despite everything else their senses told them. Why does my friend pay attention to the directions that her GPS gives her even though she's been driving the same route for 20 years? That's not a glitch in software. That's a defect in humans.
He also is quick to jump on the latest round of Toyota recalls, suggesting, before the facts are in, that the unintended accelerations were the fault of software. We now know that to be false. Those issues were largely mechanical or operator related. However, when software is around, it's an easy target that can't defend itself. We scapegoat it. Other examples he uses includes Bernie Madoff maliciously and purposedly entering bad data (how is that software's fault?) and security breaches through loss of laptops and smartphones. He cites an example of police repeatedly raiding the wrong house because the computer gave them the wrong address. How is improper police procedure software's fault? Shouldn't the police surveil the address first to verify their target is there? Why blame computers when the stormtroopers go in with guns blazing without any direct evidence that there is a threat or a suspect inside? How is software to blame there, but not in Waco or Ruby Ridge? How does the paramilitary trend in law enforcement have anything to do with software? Again, by shifting blame away from people, he absolves them of their responsibility in the outcomes and ultimately undermines the points that he is trying to make. Software is not the culprit in these cases; people are. By using sensationalisitic current events, even before the facts are in, he shows that he's not up to a serious and deep discussion of what's really happening in software.
This book does not deal with how software comes into being, and seems wholly ignorant of it. The author makes the common mistake of equating computer science with software. That's about the same as equating a physicist with a civil engineer. Although the physicist may tell you he can design a bridge because he knows the laws of the universe, do you really want a physicist in charge of something you'll drive over? Computer Science, which he wants to rename to "The Art of Computer Science" (with no nod to Donald Knuth's "The Art of Computer Programming"), is not a software creation discipline yet people keep hiring computer science graduates thinking they know how to write software. That's the problem. Computer Science is not vocational training for software creators anymore than a Chemistry program is vocational training for pharmaceutical research. However, since many people don't understand this, that there is a shortage of qualified software workers, that there isn't good training for software managers, and that everyone can shift blame to the software and the tools, the black arts of software creation and management causes a lot of problems. It's not a problem with the software--that's just the symptom of an underskilled, poorly managed, and misunderstood craft, and it's nothing new. To be sure, bad software comes out of this mess, but do you blame the culinary world when your kids burn the eggs they cook you or you get a bad meal in a restaurant? Who does Gordon Ramsey blame in Kitchen Nightmares? If you want to know more about why your software workers don't deliver, try The Pyschology of the Computer Programmer, The Mythical Man Month (or anything by Frederick Brooks), or many other books that have already dealt with the topic much better.
At one point, the author says that the senior level executives should trust their IT managers. Again with the trust. Instead of trust, the senior level executives should be holding their managers' feet to the fire to find out how much they really understand what they are doing, how they are evaluating alternatives, and what long term effects their decisions will have. They should also be holding their vendors feet to same fires so they aren't sold a bill of goods that not only doesn't meet their needs but doesn't even do what it says on the tin. However, since very few people actually understand any of this (compare with the Better Off Ted "Jabberwocky" episode), they let it slide. Again, they can shift the blame and shirk their responsibility as managers. Who gets fired when something goes wrong? It's often not the top. Compare that to the Navy, for instance. Who gets fired if something goes wrong on a ship? It's usually at least the captain of the ship, even if he did everything he should have done because he is ultimately responsible. Add careeer consequences to IT failure, and you'll change the game. Make people liable for what they do and they'll be more careful.
Having said that, I expected to see examples of companies employing good practices with high standards still run into problems that can't be blamed on anything else but the software. Are there times when you can do everything right and still lose? Where are the stories from the aerospace industry, like the Air France Flight 296 computer that decided to land when the pilot was doing a low speed pass during an airshow, or the Mars missions that miss Mars because one group used imperial units and another the metric system? There's not much breadth in this book. It's the USA Today of the subject.
I would have also like to have read a lot more personal stories from leaders of technology companies, looking back at their big mistakes. You can't effectively do that with anything current without inciting investor revolt, but how about the glitches from 20 years ago? Raymond Chen's idea on the decisions that went into Windows, the operating system that causes quite a bit of IT headaches and loss, are quite enlightening. When do the business decisions trump the software decisions? How do you balance the desire for having it now and keeping it working with the rest of your IT infrastructure with the competing forces of doing it well no matter how long it takes? How about Steve Jobs talking about any of his many failures, which he readily admits to (Apple III, Newton, etc)? Why do you have to buy expensive support contracts for Oracle, SAP, or PeopleSoft? What is the real reason those products takes so much care and feeding and cause so much frustration? What about Open Source software that still hasn't delivered a desktop operating system that normal people want to use, can't outshine Adobe's Photoshop, and still has egregious bugs despite it's "many eyes"? Why do we lie to ourselves? Is it just confirmation bias, or is it something else.
Glitch: The Hidden Impact of Faulty Software, by Jeff Papows Ph.D. PDF
Glitch: The Hidden Impact of Faulty Software, by Jeff Papows Ph.D. EPub
Glitch: The Hidden Impact of Faulty Software, by Jeff Papows Ph.D. Doc
Glitch: The Hidden Impact of Faulty Software, by Jeff Papows Ph.D. iBooks
Glitch: The Hidden Impact of Faulty Software, by Jeff Papows Ph.D. rtf
Glitch: The Hidden Impact of Faulty Software, by Jeff Papows Ph.D. Mobipocket
Glitch: The Hidden Impact of Faulty Software, by Jeff Papows Ph.D. Kindle
Tidak ada komentar:
Posting Komentar