My whole career, I've tried to follow the principle of "if you didn't write about it, it didn't happen". Writing happens in many forms: blog posts, Slack messages, issues, READMEs, release notes. Each requires a unique style: with blog posts you can add flourish whereas most issues should be to the point, concise yet comprehensive. Learning to master these styles will take time - and any new developer will need to take time to adapt. Likewise, each workplace or open source project has their own style of writing in different formats. Whether it's asking questions on Matrix or answering questions on a mailing list, if you treat one as the other you're going to have a bad time.
It's easy to get lots in an email thread.
> It's easy to get *lost* in an email thread.