Communication

Communication Channels

Slack

Our primary real-time channel. Use it for quick questions, updates, casual conversation, and time-sensitive coordination.

• Public channels first. Default to posting in public channels. Others may benefit from seeing the conversation, and it creates a searchable record.
• Threads always. Reply in threads, not in the main channel. This keeps channels readable.
• Don’t expect instant replies. People are often in deep work. If something is truly urgent, say so explicitly.

Docs (Notion)

Long-form thinking, proposals, meeting notes, and reference material. If it needs to exist for more than a day, it belongs in a doc, not a Slack message.

GitHub

All code-related discussion happens on GitHub - PR reviews, issue discussions, RFC comments. Keep technical conversations close to the code.

Meetings

We keep meetings to a minimum. When they happen:

• Every meeting has an agenda shared in advance
• Meetings start on time and end early when possible
• Action items are documented before the meeting ends
• If a meeting could be a doc, it should be a doc

Writing Well

Good writing is a superpower in an async company. We value:

• Brevity. Say it in fewer words. Cut the fluff.
• Structure. Use headings, bullet points, and numbered lists. Walls of text don’t get read.
• Context. Don’t assume the reader has your context. Link to relevant docs, provide background.
• Directness. State your point first, then explain. Don’t bury the lead.

Feedback

We give feedback directly, kindly, and quickly. Waiting weeks to mention an issue helps no one. See the Feedback section of this handbook for our framework.