Ignore concerns, not people. And only if those concerns are objectionable and unvalidated by others. A good example of how to ignore concerns would be comparin

Ignore concerns, not people. And only if those concerns are objectionable and unvalidated by others. A good example of how to ignore concerns would be comparing Dan's responses here with that of Acemarke's. Dan's is to-the-point and confident, whereas Acemarke's is... markedly less so. Really, the issue here is not how one developer communicates but how they communicate as a team. It's obvious that this self-damaging article wasn't formally approved by every Redux stakeholder-- but I also recognize that no one on the team expected for this to happen.