Why Software Gets In Trouble
Last updated on 2016-02-17
About the Book
Lyndon Vrooman wrote what many readers have said about the effect "Why Software Gets In Trouble" had on him: "I'll be honest, about half way through this book, I thought that I found it rather bland and full of things that I was already doing. This changed however as I was assessing an application that I had been working with for years and we had found some critical faults in. I started thinking more about the book and the contents of it. After re-reading it, I realized that I hadn't been looking closely enough for faults, only going just beneath the skin. As I started to apply more and more of the information within, I began to realize more and more of what I had been learning was adding tremendously to the quality of the product. In short, after thinking more and more about this book, it's quickly gone to one that I recommend to everyone that I work with."
Another reviewer, Joe Strazzerel recounted the contents: "Jerry describes many of the ways errors occur, the correct way of thinking about errors (such as "Errors are not a moral issue" and "Quality is not the same thing as absence of errors"), how companies and processes get into a state where errors are more likely to occur (increased pressure, high levels of stress, poor estimation, lack of control, etc), and the effects of breakdowns."
"This book is fairly short, yet surprisingly thorough over its seven chapters:Chapter 1: Observing and Reasoning About ErrorsChapter 2: The Failure Detection CurveChapter 3: Locating The Faults Behind The FailuresChapter 4: Fault Resolution DynamicsChapter 5: Power, Pressure, and PerformanceChapter 6: Handling Breakdown PressureChapter 7: What We've Managed To Accomplish""For me, this was a very timely book. My team is going through some of the same pressure patterns Jerry writes about. For virtually every point made, I found myself saying 'I remember when that happened,' and sometimes 'That's happening right now!'""If you are a Software Testing professional, you should read this book. You should then give a copy to your manager, and to your manager's boss. Then, be prepared to discuss with them the realities of software development from a tester's point of view. After reading 'Why Software Gets In Trouble." you'll almost certainly have a more enlightened (and hopefully more receptive) audience."
And Don Gray wrapped up by adding in his review with a case example from one of his clients: "After three quarterly 'successful' releases a company had 453 defects opened in a single day against the 'successful' releases."
"Many books exist for any given programming language. Every developer had two or three at their desk. One book on software engineering may exist for every 100 language books. Maybe not. I noticed one developer had one.""453 defects don’t suddenly happen. Something in the process and culture allowed them to build until they could no longer be ignored. It seems to me someone at the company might benefit from learning about system dynamics and the reasons behind software errors.""Why Software Gets in Trouble is the only book I know of that explores the systemic dynamics and reasons behind software errors. Using stories, graphs and Diagrams of Effects, this book explores how different software cultures: * notice and think about errors * detect failures * locate the faults behind the errors * resolve faults * apply and handle pressure"The content applies to both managers and developers. If you’ve wondered why you keep experiencing the same patterns concerning shipping software, this book will help you understand why.""NOTE: If you’ve not read How Software is Built, you might find reading Why Software Gets in Trouble's appendices on Diagrams of Effects and Software Engineering Cultural Patterns helpful prior to starting the main text."
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms...