I can highly recommend this book to individual contributors and those early in their leadership journey. It provides a good discussion of what makes a healthy team and how to work well in one. It talks about good leadership and company cultures. It even talks about why marketing (caring about first impressions), customer service (listening to your customers), and company politics (coordinating large groups of people with multiple goals) aren't always as bad as they're made out to be.That said, i...

Great book. Sometimes we just need to be reminded the obvious, in this industry we are just people working with other people. Hopefully this book will make people reflect and change some behavious we assume as correct.

◆ “Leader” Is the New “Manager”▪ Traditional managers worry about how to get things done, while leaders worry about what things get done…(and trust their team to figure out how to do it).Another big reason for not becoming a manager is often unspoken but rooted in the famous “Peter Principle,” which states that, “In a hierarchy every employee tends to rise to his level of incompetence.” Most people have had a manager who was incapable of doing her job or was just really bad at managing people,7

I can’t really disagree with anything in here but similar to what other reviewers said, it’s mostly stuff you’ve probably heard about before (and I say that as a person who’s not a manager). It’s also fairly light on practical advice. That being said I still appreciated it as it helped to cement some of the things I already sort of knew and I think it’ll be a great reference to come back to later on if I ever do become a manager or lead of something.

Definitely a great book on its own but since this is a follow-up on Team Geek, it's mostly reiteration and repeating Team Geek's ideas.

The purpose of this book is to help people improve their collaborate with others. The authors introduce it as “social challenges of creative collaboration.”Cool tech history note. The authors worked on the Subversion open source project; and later at Google on Google Code.The book reads as a series of essays; it’s easy to pick up a chapter or section without going end to end.The “core traits to remember” are abbreviated “HRT” and stand for humility, respect, and trust.Hat tip: Andrés Bastidas. R...

The second edition of Team Geek was renamed to Debugging Teams to reflect a partial rewrite to make the book more accessible to people who aren't on software engineering teams. But, the focus is still very much on debugging a software engineering team. That said, there is a lot of value for non-engineers, but expect to find yourself flipping through several less relevant sections very fast.If you're on a software engineering team, I highly recommend this great book with very relevant, useful adv...

First things first: If you read or ever heard about the famous "Peopleware: Productive Projects and TeamsPeopleware: Productive Projects and Teams", you can consider "Debugging Teams" a perfect companion for the issues pertaining to modern information technology teams and their dynamics.The book's strong point stems from the fact that the authors have experience both in managing and be managed, as well as dealing with complex open source community and the dynamics of their members. They don't su...

This is a great book to read as a team. It's full of easy to understand and practical advice. This edition of the book is intended for a larger audience than just programmers but all the good examples are from programming teams.I liked the theme of HRT that's throughout the book -- Humility, Respect, and Trust. Some of the ideas I found worth writing down.* Fail early, fail fast, fail often -- don't work in isolation or be afraid to share work in progress* Ask questions to guide other to their s...

Couldn't get past the first chapter.A very poor example out of the gate of Michael Jordan's 90s Bulls. Emphasizing that it wasn't him but the team that won all those championships - true it was the team, but would the team have won without MJ? I don't think so. Could MJ go to a semi-competent team with Scotty Pippen tier player on his side and win? For sure.A few pages later the authors drive the point of the most important aspects in successful teams - respect/trust/humility which directly cont...

This book really changed me and had me see the value in incorporating a mission statement, regardless of what team you’re on, or level in your company. The principles in the book speak to Humility, Respect, and Trust, and how each of those is integral for building the best team. It’s a very quick read, but I highlighted a lot of quotes from it. Probably the best part speaks to how IT folks get thrust into management, it’s usually not a path we want to go down. How do you traverse that? Get this

This book about managing and troubleshooting teams. MUST HAVE for any leader (both technical or management). This book is great. It helped me to understand how teams are working, how to deal with people in a better way, how to build a better culture in the organization. It has a lot of good examples from authors on how to deal with different situations in the work. I love the examples and I can say I've been there and faced it.I'm pretty sure this will be a handbook for me for the next few years...

I read this book after listening to a podcast. It's been described as “How to Win Friends and Influence People for programmers”.Debugging Teams is supposed to be a new, less software-developer-specific version of Team Geek. I haven't read Team Geek, but Debugging Teams still had pretty much that was focused on software-related things. I thought this was a good thing. Sure it could generalize.The main thesis of the book is their “HRT”: humility, respect, and trust. These are all good things to ha...

People are the main component of a project. That said, it's extremely important to know how to build a solid team. The authors cover a lot of scenarios of collaboration with people inside your team, how to lead them, how to shield them against poisonous people, how to collaborate with people from another areas of the company and with the users of your product.Highly recommended (whether you are an individual contributor, a team leader or intend to become one).

Primary theme of the book is HRT: Humility, Respect, and Trust.This book content is based on the authors' experience and anecdotes, along with summaries from a few other management books. There are no studies cited and no quantification. The book provides best practices with a focus on what to do rather than why or how. No novel insights. The software category covered is shrink wrapped (see Joel's Five Worlds).

Loved this book! I wish I had read this much earlier, probably when I started my career. This book is not just meant for people managers, but also for individual contributors who have to work together in a team to build great products. The experience of the authors enriches this book with an abundance of relatable examples.

Pretty okay book. Lots of advice is just common sense, but there are parts here and there that may be useful in the future, especially if you never encountered situations described in the book.Definitely a good read for people who never read anything like this before. Maybe if all people followed the advice here, it'd be a better place. :)

Unlike ordinary development books, each page was a useful book, full of different best practices. Each page contains suggestions that you can adapt to daily work life. In addition, they embody the points that are tried to be explained with examples from their own lives. In short, I found the book very useful, I recommend it.

From the outside, it looks managerial. But really it's a guide on how to organize your project communities, build trust with peers and users, and keep a healthy team culture.Some stuff is straight forward of you've worked at companies like Facebook or Google. But it's always nice to have explicit call outs.I'd recommend it to anyone who is a main contributor to a project, or leads a team.

Great book although a bit bland. The book has great overall principle, however I was hoping for more detailed solutions (it has after all "debugging" in the name)I was also a bit disappointed they dialed down on technical stuff to reach a bigger audience.Nevertheless, a good book if you're expectations are different

How I wish this book existed when I started leading teams several years ago! IMHO, this is one of the very best books on team leading and general corporate life. A must read for anyone working with teams!

The authors talk about some problems and bad behaviors that can affect teams. I definitely saw myself in some of the "don't do this" examples. Whoops. If I had read this book ten years ago (or even one year ago) my life today would be very different. Live and learn, right?

Quick, entertaining, and surprisingly dense book detailing what components make up successful software engineering - or really any! - teams. I didn't exactly learn anything new reading this book but find incredible value in this book being citable.Worth the read.

Very good book for matured software engineers who are now stepping into more management-like or leadership-like roles. (Especially the first two parts. The last part focused on the users was IMHO a bit off-topic.)

I really liked this book, taught me that creating software is not just about writing code and that people is more complicated than software. Also, taught me that we can be better developers/leaders/persons if we apply humility, respect and trust in all our actions and relationships.

Fantastic book, lots of practical team management and building experience. It was perfect to refresh concepts I had learned from Peopleware and Code Complete 2

It is a well-worth quick read if you are an engineer who wants to maximize your impact by picking up soft skills.

Great book, a lot of real-life situations in software development may be useful in the future, patterns, and antipatterns for managing a team of software engineers.

This very short book covers a lot of commonsense stuff about how to manage teams and users. It ultimately falls short in practical examples.

Basic stuff (and no big surprises for me personally; much of it is in the curriculum at work), but well written & engaging.