- Hardcover: 208 pages
- Publisher: Prentice Hall; 1 edition (September 4, 2010)
- Language: English
- ISBN-10: 0132160633
- ISBN-13: 978-0132160636
- Product Dimensions: 6.4 x 0.7 x 9.3 inches
- Shipping Weight: 14.4 ounces
- Average Customer Review: 29 customer reviews
- Amazon Best Sellers Rank: #4,110,831 in Books (See Top 100 in Books)
Enter your mobile number or email address 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.
To get the free app, enter your mobile phone number.
Glitch: The Hidden Impact of Faulty Software 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
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.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
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.