The art of software testing

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

This record preserves its author, date and source link. Open HN to read the full context.

There was a slim volume called the "The Art of Software Testing" that I borrowed once from my mentor. In it, the author posits the following perspective: a successful test is not one that finds zero errors, a successful test is one that finds errors.

"Becoming a Technical Leader" by Gerald Weinberg Unconventional perspective on management "How Buildings Learn" by Stewart Brand One of the best books about designing long-term architectures. Excellent coffee table book "Envisioning Information" by Edward Tufte "Walt Disney" by Neal Gabler Excellent biography of maybe the greatest imagineer ever "The Art of Software Testing" by Glenford J. Myers ~100 page classic. The central premise is that the successful test is one that finds bugs/issues not one that doesn't.