Solving a technical problem is relatively easy: there tends to be precedence, easily accessible data, black and white results, and a knowledgeable community to lean on when you get really stuck. People problems are stickier; there are far more variables, no tests you can write, no debugger to use. What best practices can be employed to troubleshoot people problems? What if we are the problem?

In this light-hearted experiment in self-examination, we’ll focus on our biggest issues as developers and community members. We’ll examine what’s broken, what works, and some useful people katas to help us grow.

• Be the kind of person you want to work and collaborate with
• Managing expectations
• Learning to hear and say “no”
• Effectively communicating