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:
From LinkedIn
â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?