Lessons Learned in Software Testing: A Context-Driven Approach

The already mentioned The Pragmatic Programmer, 20th Anniversary Edition is so far the best I have read. It's not overly specific to one single thing, it tries to teaches general principles and good practice.[1] I also have a personal recommendation for when you want to better understand testing, QA, or want to/have to work with QA people. [2] [1] https://pragprog.com/titles/tpp20/the-pragmatic-programmer-2... (https://pragprog.com/titles/tpp20/the-pragmatic-programmer-20th-anniversary-edition/) [2] https://www.amazon.com/Lessons-Learned-Software-Testing-Cont... (https://www.amazon.com/Lessons-Learned-Software-Testing-Context-Driven/dp/0471081124)

There is a class at Georgia Tech I colloquially referred to as "making sure your coworkers don't hate you." It covered design patterns, software testing, and project management. I'd tack on a basic knowledge of databases to that. These are things you can gain a true functional knowledge of in a couple of weeks, and which not knowing might make senior engineers hate working with you. So to mimic the class: The Mythical Man Month Design Patterns - Even if some of the particulars are not as relevant, it still provides a useful framework for thought. Lessons Learned in Software Testing: A Context-Driven Approach I'd also add Harry Potter & The Methods of Rationality. A lot of engineers can think empirically, but its not their first reaction. Going through this book helped make it second nature for me. Can't remember if a certain data structure is immutable? Now I'll write a couple of lines of code to see rather than go looking for documentation. A lot of big problems start as false assumptions. Having the instinct to think to test them and knowing how to will prevent a lot of wasted effort, regardless of your role.…