🚴‍♂️

Culture

1 article Pranav By Pranav

Articles about culture

Communication

We’re a remote team, so clear, thoughtful communication helps us work well together. We prefer written, asynchronous communication whenever possible, giving everyone the context and time they need to contribute. Values Positive Communication: There are a lot of things broken at a startup. But many things are working well, too, if the startup is still staying afloat. So while we might have inhibitions, It is always preferable to communicate from the perspective of "half-full cup vs. half-empty cup." This leaves a space for presenting the half-empty cup (risky situation) narrations in their seriousness. So we suggest having a viewpoint where you look at things as something that could improve vs. looking at everything from the perspective that it's broken. Communicate in public by default Keep work conversations in public team channels by default. Whether you’re asking a question, discussing an idea, sharing progress, or making a decision, use the relevant Slack channel or a shared GitHub issue or pull request. This helps everyone stay in the loop, gives others a chance to contribute, and makes answers easier to find when someone has the same question later. Reserve DMs for sensitive or personal topics, or information that shouldn’t be shared with the broader team. If a DM turns into a general work discussion, move it to the appropriate channel or issue and share the useful context there, without exposing anything private. “Public” here means visible to the relevant team. It doesn’t mean sharing confidential company information on the internet. Written communication When you ask a question or share an idea, include enough context for others to understand and respond. Use threads to keep related conversations together. Keep product discussions and decisions in the relevant GitHub issue or pull request. Document internal processes in Notion or the handbook. If a call or pairing session leads to a decision, add a short summary where the team can find it. Slack Slack is where we communicate as a team. Pick the most relevant channel, and use threads for follow-up conversations. Give people time to respond; async communication doesn’t mean everyone needs to be online all the time. Use @channel and @here sparingly, for urgent or time-sensitive things that need the channel’s attention. Our community also uses Discord. Keep community questions and answers in the appropriate public channels whenever possible, so others can benefit too. Pair programming with Tuple Our engineering team uses Tuple for pair programming. Feel free to keep yourself online when you’re available to pair, so teammates know they can reach out. If you make a decision together, add a quick note to the relevant issue or pull request so the rest of the team has the context.