It’s time to recommend some books, for we should prepare some soft skills to become an agile developer and work more effective and efficient. All three books don’t have code, and will not explain the programming technology, they focus on engineering practices, people in development process, etc. I have finished book 1) and 2), and I am reading 3).
1) <The Pragmatic Programmer: From Journeyman to Master>, 5 stars in Amazon.
Customer review:
Hunt and Thomas vastly exceeded my expectations. This book is never dry, often humorous, and always educational. They don’t always say what you expect them to say (e.g., about commenting code), and I didn’t always agree with them, but every sentence is full of thoughtful analysis.
One of the best features is their incredibly practical advice — while yes, this book does teach philosophy and encourages thought, it also provides many immediately-implementable suggestions.
2) <Practices of An Agile Developer: Working in the Real World>, 5 stars in Amazon
Customer review:
In my own work, I am struggling with various agile vs. non-agile practices, but sometimes it can be hard to see why a non-agile practice is worse in the long run than an agile practice. This books goes a long ways toward identifying the problems with non-agile practices by identifying an agile practice, then showing the benefits of following it as well as the result if it isn’t followed. Throughout the book, a little angel and a demon show up-the angel illustrating a “good” practice, and the demon illustrating a “bad” practice. This makes the book a fun read and I think really helps in illustrating the authors’ points.
3) <Team Geek: A Software Developer’s Guide to Programming Well with Others>, 5 stars in Amazon
Customer review:
Brian Fitzpatrick leads Google’s Data Liberation Front and Transparency Engineering teams. Ben Collins-Sussman is one of the founding developers of SVN and now manages the engeneering team for the Google Affiliate Network. The Book has a clearly defined goal – to help programmers become more effective and efficient at creating software by improving their ability to understand, communicate with, and collaborate with other people.
And that is the essence of this book. It explains why each relationship (not only related to Software projects) should be based on Humility, Respect and Trust (HRT).