What Testing Books Influenced You?
The author of the “Agile Testing” blog recently did a nice blog post on a list of 25 technical books that influenced his career. They’re listed here, “in somewhat chronological order of my encounters with them.”
- “The Art of Computer Programming“, esp. vol. 3 “Sorting and Searching” – Donald Knuth
- “Operating Systems” – William Stallings
- “Introduction to Algorithms” – Thomas Cormen et al.
- “The C Programming Language” – Brian Kernighan and Dennis Ritchie
- “Programming Windows” – Charles Petzold
- “Writing Solid Code” – Steve Maguire
- “The Practice of Programming” – Brian Kernighan and Rob Pike
- “Computer Networks – a Systems Approach” – Larry Peterson and Bruce Davie
- “TCP/IP Illustrated” – W. Richard Stevens
- “Distributed Systems – Concepts And Design” – George Coulouris et al.
- “DNS and BIND” – Cricket Liu and Paul Albitz
- “UNIX and Linux System Administration Handbook” – Evi Nemeth et al.
- “The Mythical Man-Month” – Fred Brooks
- “Programming Perl” – Larry Wall et al.
- “Counter Hack Reloaded: a Step-by-Step Guide to Computer Attacks and Effective Defenses” – Edward Skoudis and Tom Liston
- “Programming Python” – Mark Lutz
- “Lessons Learned in Software Testing” – Cem Kaner, James Bach, Bret Pettichord
- “Refactoring – Improving the Design of Existing Code” – Martin Fowler
- “The Pragmatic Programmer” – Andrew Hunt and David Thomas
- “Becoming a Technical Leader” – Gerald Weinberg
- “Extreme Programming Explained” – Kent Beck
- “Programming Amazon Web Services” – James Murty
- “Building Scalable Web Sites” – Cal Henderson
- “RESTful Web Services” – Leonard Richardson, Sam Ruby
- “The Art of Capacity Planning” – John Allspaw
What about you? What technical books – specifically testing books – have made the biggest impact on your learning/career?
