Books

A list of books that have helped me improve my Testing and thinking around testing.

TLDR; Do you test with individuality? Do you release work that reveals and harnesses your creativity? You can. Take heart from people like Stafford Beer, Charles Dodgson, Buckminster Fuller, William Blake and more. “I will not Reason & Compare: my business is to Create”

TLDR; A treatise on non-software bugs, written in 1730, but still with lessons to learn.

Written in 1730 by John Southall

Bug Prevention and Detection has been a problem throughout the ages.

How to improve your software testing skills, by following these strategies, that’s how. Based on a quick book recommendation - Isaac Newton by James Gleick I want to explain how we can learn lessons from his approach to his work and career.

TLDR; It still has moments of well worth reading but it also has sections where you hope no-one follows the instructions.

TLDR; Abstractions are not new, have never been easy, and have always been important when architecting our Systems.

TLDR; Learn your skills and techniques. Then learn your tools. Mastery of tooling can lead to new techniques and new ideas. Continue to learn your theory, skills and techniques. Continue to master your tools.

TLDR; older computing books and papers have a lot of really useful information - read them. Programming has an ’easy to automate’ level called ‘coding’, with a similar relationship to ’testing’ that ‘checking’ has. Assert as well as Check. Developing includes Testing and Programing and other stuff.

During the creation of Dear Evil Tester I posted a running commentary with information about the self publishing process. This post collates the smaller posts together in an edited format and acts as a primer of the self publishing process.

TLDR; The learning experience that Steve Martin describes relates fairly well to many jobs, many of us don’t go the extra mile that Steve Martin attributes to his success.