This book was released in 2004, and I started working as a software engineer about 10 years later. If I had read this book then, I wouldn’t have understood the impact that the practice of XP (Extreme Programming) could (and would) have on myself and the work I do. Doing things the “wrong” way—meaning less effective and more expensive—is, in my opinion, one of the best ways to understand the need and appreciate the benefits of doing it differently.

It’s not even specifically about software engineering either. XP has had big and positive effects on my personal life as well. Forming habits, measuring outcomes, and continuous improvement.

The book mentions the importance of having a community (around XP) that you engage in. A safe space where you share your thoughts and worries and get constructive feedback. This can be on the internet, meetups, or in the workplace. I was introduced to XP in the workplace which meant that I already had a community to engage with (even if it was just one other person). It helped immensely with understanding and putting XP to practice.