#948 in Business & money books
Use arrows to jump to the previous/next product

Reddit mentions of Debugging Teams: Better Productivity through Collaboration

Sentiment score: 3
Reddit mentions: 5

We found 5 Reddit mentions of Debugging Teams: Better Productivity through Collaboration. Here are the top ones.

Debugging Teams: Better Productivity through Collaboration
Buying options
View on Amazon.com
or
O REILLY
Specs:
Height8.43 Inches
Length5.85 Inches
Number of items1
Release dateOctober 2015
Weight0.6393405598 pounds
Width0.43 Inches

idea-bulb Interested in what Redditors like? Check out our Shuffle feature

Shuffle: random products popular on Reddit

Found 5 comments on Debugging Teams: Better Productivity through Collaboration:

u/daredevil82 · 2 pointsr/webdev

Nice list! I'd add Debugging Teams to that list too. I love Five Dysfunctions and Manager's path

u/beliefinphilosophy · 2 pointsr/smallbusiness

The Book, Debugging Teams is fairly short and creates some super great, easy to implement, powerful skills for any manager or team.

u/ildiroen · 2 pointsr/devops

The DevOps Handbook, Team Geek and Debugging Teams come to mind.

I don't think there is something specifically for "devops managers" (what is that even?). General leadership books would work for you as a manager I suppose. Just keep the principles of DevOps in mind when you do manage away.

u/frenchst · 1 pointr/cscareerquestions

You're going to find yourself in a position where you'll need to communicate external dependencies to your team, and also where you'll need to communicate the work you do outward. Focus on how you can deliver these messages in the most effective manner so that everyone hears them.

Develop a culture of rigor. If you want a product that's stable, secure, performant, and maintainable, you should state that very clearly, and bring all your internal discussion back to those tenets. If you don't have them already, invest in testing, real-world monitoring and error reporting, and code review.

Code review is the worst place to make architectural decisions. It's expensive and difficult to make changes when you catch them at this stage. If you're catching architectural issues at code review, it means you don't have enough process up front to design the system/code correctly.

It's a powerful thing to say "I don't know" or "I was wrong". You'll develop a trust with your team that they can depend on you to be searching for the right answer, even when you don't know.

Have a weekly "dev team meeting". Having a forum every week where you can talk about the tactical approach to the project can be really helpful. As the name suggests, keep it to just the dev team, and possibly the manager if they are extremely technical and directly involved in helping the team execute on the project.

Finally, I can't recommend this book highly enough. It's a quick read, and you'll come back to it many times. https://www.amazon.com/Debugging-Teams-Productivity-through-Collaboration/dp/1491932058