Debugging Teams: Better Productivity through Collaboration

The book is about simple but very powerful tactics when applied in daily work. Great content!

Loved the format and easy going writing. Underneath that glossy surface is a book packed with solid advice for any person leading one or more software team.If I should list anything negative it could be that the open-source example situations might be a little bit hard to translate into context for the enterprise developer. That's compensated with a fair share of enterprise stories too so there's no big problem.Thank you for a great book

Honestly, there wasn't anything here that was 'Wow, I didn't know that', but I wish I had read something like this 10 years ago.

Great book thats not only talking about Team work but also how to exercise basic social traits like humility

I enjoyed this book so much that I made a somewhat impulsive decision to make it required reading in my software architecture class. Each semester a percentage of my students consistently struggle to work successfully in ad-hoc teams. This book is the antidote. It empowers them with specific approaches to dealing with nearly every common teamwork malady. Great work by both authors!

Full of insights, and clear definitions and guides on common situations. A must read for those who are individual contributors as well as those in management.

These guys are as insightful as they are efficient, as good-humored as they are pragmatic.I'm a communications person and I learned some great things from this book. Plus which it's always diverting to see into the engineering mind.

I especially enjoy the HRT principle - humility, respect and trust. The authors explains those principles in terms laymen can understand.

I have been a software developer for 16 years on many projects. Like many other developers I love the technology but often struggle with people. Developers often complain about language features and software design and other technological gripes but in my experience it is people and politics that cause the vast majority of the stress and confusion in the workplace. In this way software development is much like any other profession.This book does not have all the answers but it is a wonderful start. There is a great deal of wisdom and a great many life lessons contained inside. I am still learning to apply these lessons to my working life but can already see the benefits.In addition the book is succinct. It is a definite problem with most non-technical computing books that they are bloated beyond reason ("The Art of Agile Development " is one such book where the message is all but lost in a confusion of poorly edited rambling).Debugging Teams is a book I love and wish had been available when I started my career!

This book shows readers how to be good employees. The anecdotal evidence in it is mostly Google-specific. As Google is a rather unusual company, some of the advice given in the book may not be applicable to normal companies where money is tight and people fight to keep their jobs.

The authors obviously know their stuff, and each page provides insight that is worth taking note of. With real suggestions and advice, I highly recommend this book to anyone working in a team, especially within the software industry.This will be kept on my desk as a ‘go to guide’ from now.Thanks to Brian and Ben for sharing their knowledge with the rest of us.

Molte conferme, qualche esame di coscienza. Un libretto da leggere assolutamente, e rileggere, perché chi si sente un "tecnico" può spesso finire col lasciare in secondo piano cose molto importanti per la serena convivenza nel team e anche per la propria carriera.

It's straight to the point and gives practical advice. Economy if every manager reads this book and applies to himself and to his team, then we all will have less stress and become more productive.