3 ms·
Written communication is a challenge for some people. Not everyone is as good of a writer and this skill does not map to coding skills. In the team I'm currentl
by jillesvangurp 7y ago
Written communication is a challenge for some people. Not everyone is as good of a writer and this skill does not map to coding skills. In the team I'm currently in, this is definitely a problem and I notice some people are not used to doing this and are effectively struggling to be part of the ongoing discussions.
I've met more than a few engineers that in meetings don't tend to speak up and in chat channels mostly don't engage. Chat channels tend to be dominated by the same people that are also dominating meetings. This is not necessarily a good thing.
For better or for worse, this causes side channels to pop up and this is where most of the discussion happens. This is a problem because it by design excludes people. But it's needed because you can't speak freely in a channel where everybody in the company listens in, including management, individuals you don't get along with, etc. Pretending this is not a problem is not helpful.
In OSS projects, there's a pattern of frequent contributors to be disciplined about how they use communication tools. IRC historically is the place where people discuss in an unmoderated forum. It's noisy and chaotic and often not pretty. But it's not necessarily there for documenting decisions. That's what issue trackers or mailing lists are for. Those tend to have a narrower scope of what is on and off topic.
Translating chats into actionable items, or documenting outcomes of discussions is the key thing to do. The larger the project, the more obvious this need.
In a corporate setting, the tools for this are comparatively poor and not that good for facilitating asynchronous communication. E.g. Atlassian's tools are pretty popular but not great for async stuff. IMHO Jira is slow to interact with and this obstructs effective communication. It's notifications, default settings, etc. are basically completely wrong and counterproductive. Absolutely everything requires multiple mouse clicks. IMHO Github issues is vastly easier to deal with for engineers; it's also easier to refer to commits and pull requests there. And with github actions integrated, you also get insight into the status of CI. Likewise conflucence is a PITA to use compared to managing markdown files in a git repository or co-authoring a document on Google docs. Slack is nice but way too noisy for communicating things unless you have read only channels that are used for things like announcements.