BROADCASTS.com

b'

In this episode, Dave and Jamison answer these questions:

\\n
1. \\n

   How do you politely tell a reviewer politely, \\u201cYour suggestion is stupid. I will not do it\\u201d when you get stupid review comments. If you don\\u2019t do it then the pull request can\\u2019t move forward because of unresolved issues. If you do it, then you\\u2019re compromising your design you\\u2019ve worked weeks on for some fly-by random comment.

   \\n
\\n
2. \\n

   A few months back, I volunteered as co-facilitator for my department\\u2019s NodeJS Guild meeting. At first, it was a struggle to get people to present. But I tried to lower the bar more and more until it was easy. I asked for 10-15m presentations, and eventually I realized people are happier \\u201cKicking off a discussion\\u201d than they are \\u201cgiving a presentation\\u201d. All the listeners are more engaged too, at least after the first 2 meetings doing this.

   \\n\\n

   Now I want people to share half-baked code, or problems they are struggling with, as part of our discussions. I want people to be able to be vulnerable. If we don\\u2019t collaborate on common problems until we feel they\\u2019re polished and won\\u2019t reflect badly on us, then we will all waste time solving the same problems.

   \\n\\n

   I also want this to scale across 15-25 small scrum teams. I think success could be my demise\\u2013if we have good discussions, then more people will come, but people won\\u2019t want to be as vulnerable with a larger group.

   \\n\\n

   In general, I think my own scrum team is very open and vulnerable to each other, but the remote work in the deparment has created distance. I want to help create more collaboration on similar problems and solutions.

   \\n\\n

   What would you do to keep this going, and improve it?

   \\n
\\n