|Format||Full Book||Sample First 20%|
|Online Reading (HTML, good for sampling in web browser)||Buy||View sample|
|Kindle (.mobi for Kindle devices and Kindle apps)||Buy||Download sample|
|Epub (Apple iPad/iBooks, Nook, Sony Reader, Kobo, and most e-reading apps including Stanza, Aldiko, Adobe Digital Editions, others)||Buy||Download sample|
|PDF (good for reading on PC, or for home printing)||Buy||No sample available|
|RTF (readable on most word processors)||Buy||No sample available|
|LRF (Use only for older model Sony Readers that don't support .epub)||Buy||Download sample|
|Palm Doc (PDB) (for Palm reading devices)||Buy||Download sample|
|Plain Text (download) (flexible, but lacks much formatting)||Buy||No sample available|
|Plain Text (view) (viewable as web page)||Buy||No sample available|
on April 12, 2011 :
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.
(reviewed long after purchase)
on Feb. 25, 2011 :
"Why Software Gets In Trouble" is part 2 of the latest edition of Weinberg's "Quality Software" series.
In it, 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 Errors
Chapter 2: The Failure Detection Curve
Chapter 3: Locating The Faults Behind The Failures
Chapter 4: Fault Resolution Dynamics
Chapter 5: Power, Pressure, and Performance
Chapter 6: Handling Breakdown Pressure
Chapter 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.
One note: You should read the appendices first, so you will understand the diagrams and references to "Patterns" scattered throughout the book.
A disclaimer: Jerry put out a call for reviewers on his website (http://secretsofconsulting.blogspot.com/2011/02/free-books-looking-for-few-more-book.html) and gave a free e-copy of this book to those who would agree to post a review. Since I enjoyed his book "Perfect Software: And Other Illusions About Testing" so much, I agreed - this is my review.
(reviewed within a month of purchase)
on Dec. 10, 2010 :
Why Software Gets in Trouble
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.
If you’ve not read How Software is Built (http://www.smashwords.com/books/view/25293), you might find reading the appendices on Diagrams of Effects and Software Engineering Cultural Patterns helpful prior to starting the main text.
(reviewed long after purchase)