How to break software

I was walking to another building at work the other day, and I came across a tech talk that was just getting started. It was by a guy named James Whittaker, and called "How to break software". The talk was based on research done for a book of the same name. I didn't have anything that couldn't wait an hour, so I grabbed a piece of floor and listened in.

This Dr. Whittaker was engaging and funny, but pretty amazing from a technical perspective. Over the course of many years, he and his students distilled 10,000 reported software failures found on the Net to just four root causes. And so he then figured that you can test in those four areas and make your software better by finding nearly all the bugs before they ship out with your product.

I'm definitely buying his book.

Comments for: How to break software

Post a comment
Name:


Email Address:


URL:


Comments:


Remember info?