This book was given to my team and I as a member was leaving. If you've ever had to be in any kind of leadership position (or even if you think you *might* be in a leadership position one day, or even if you don't think you will for that matter) this book is for you. There are a lot of great lessons-learned and anecdotes on teams, interactions within and without them, and how to be a more effective leader. I'd highly recommend this book to anyone in the software development industry. This would be a good first book on management for developers. After managing for the last 4 years or so, I didn't find the book particularly interesting or new; I often found it a little too proud of itself. I read this part of a manager book club at work; I enjoyed the conversation that came out of having read the book more than the book itself.The ideas that did resonate with me from the book that were either things I had distinctly thought of, or that were a good reminder:- ask my reports "what can I do for you me?"- ask my reports "what do you need from me?"- my main job is to clear obstacles from my reports so they can get work done faster. This means not knowing answers is ok, but knowing who does know the answer is vital.
Solid principles applicable to any community. Critical to successful software teams.
—Aminarocs
Useful read for understanding how engineering works in a larger organization.
—fitznork
Mostly common senses, but easily overlooked facts.
—Zee
good book for developers
—Michael
