It’s interesting to see what inspires us as testers, in this case, books. So what non-testing books are you reading that influence your testing?
Here are some of the answers so far:
“The Book of Why: The New Science of Cause and Effect” - Pieter Withaar
“Really enjoyed reading ‘Blood, Sweat, and Pixels’ by Jason Schrier, a lot interesting production and development lessons from various levels and I worked on one of the games covered.” - Kevin Smale
A few that come immediately to mind as influencing my thoughts and practices: “Overcomplicated”, “The Landscape of History”, “The Glass Cage”, “Surpassing Wonder”, “The Half-Life of Facts”, “Lost in Math”, “Houston, We Have a Narrative”, “The Logic of Failure”, “Antifragile”, “The Most Human Human”. “The Shape of Inner Space”, “The Death of Expertise”, “Finding God in the Waves”, “But What If We’re Wrong”, “Thinking, Fast and Slow”, “Black Box Thinking”, “Ubiquity”. - Jeff Nyman
" I highly recommend The Age of Surge by Brad Murphy. This taught me some very valuable insight about how code isn’t the only thing we need to know how to measure and test properly." - Sean Davis
“Black box thinking by Matthew Syed” Oleg Pantsjoha
“The Black Swan (Taleb’s), An Introduction to General Systems Thinking (Jerry Weinberg), and How to Lie with Statistics (Darrel Huff).” - João Farias
““Checklist Manifesto” by Atul Gawande.” - Linda Paustian
“The Courage to Lead by Brian Stanfield remains one I go back to over and over again. Asking how comprehensive is your model? How do I create structure and processes that allow and encourage people to express their care for quality across the organization? Etc” - Nate Custer
" “The Lean Startup” by Eric Ries changed my thinking around quality" - Ryan Quellhorst
“Writing Solid Code by Steve McGuire. When I started out testing it was from a business usage position. Then when I started working more closely with developers, I felt the need to understand what good coding practice was like. At the time, Microsoft Visual Basic was on the rise, and this book described how to write code to meet business processes. There’s probably newer books to explain newer methods. I’d be interested to see what others used to get their testing head in the developers game.” - Iain Macmillan
“Forensics and Criminology” - Gemma P
“Accelerate: The Science of Lean Software and DevOps.” - Julio Eliseo Valls Martinez
So what are your books?