I am currently reading Building Software Teams, which is the companion/follow-up to Building Maintainable Software.
It is a thin book focusing on the thing around building software in a way that it can be maintainable/clean/etc. If none of the topics discussed in this book are new for your team, then it's good: revision control, continuous integration, test automation, deployment automation, ...
It presents the motivation why these things are important. The book is more for team leads and managers. But it can also be useful to developers, especially as backing towards management why certain things should be done.
I have not been in a role of managing a team, thus solely working on a feature I was tasked to do. There were times when I thought that management, software cycle, test automation, etc can be improved. This looks like a great book and will be on my reading list. Thank you for pointing it out.
Always wondered - how do you read a collection like that? is it more for reference based on what you are working on at the job/project? Unlike other types of books - tech books require almost immediate application for the learning to stick. What are your thoughts?
Thank you for asking. I only focus on reading 1 or 2 books at the moment. While I can read other books when I want to get my mind off to a different topic, or just to read for fun and breadth of knowledge. I find it when I am reading for fun, it sticks better.
You can skip the interview books but the others read them from cover to cover. I would also recommend to come back to this list 10 years from now and read them again. That is what I'm doing with my collection.
I'm curious - most of these books can easily be counted as interview prep material, are you preping or you just like these kind of books? Cause they can be quite exhausting. Also how long does it take for you to finish CTCI or EIP? :)
Yeah. I was preping but I also like algorithms book in general. I also alternate between software engineering and coding to get more broad knowledge. To be honest, I never finish those books, only 25% or less. I like to have them as a reference when needed though.
I just like anything about books... Thanks for this
I once read Cracking the coding interview, it was awesome other than that every other books are new for me thanks for the listings ... :)
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.