How We Contribute Individually
We actively create space for all voices to be heard because our products are better when they reflect the diverse viewpoints and backgrounds of the team that’s building the product.
We’re kind to and thoughtful of each other because we need to offer up our creative output for praise or criticism every day and keep coming back for more.
We seek feedback early and collaborate with trusted thinking partners because if we can’t explain it simply, we don’t understand it yet.
We actively participate in the PR process and review our teammates’ code routinely because it provides both the submitter and the reviewer with opportunities to learn, teach, and establish even broader shared context.
We write automated tests covering the behavior of each pull request as a vertical slice because tests serve as living documentation and regression protection, and nobody’s going to loop back and write good tests later.
We shepherd our own PRs into production because responsibility is the corollary of pride in ownership.
We don’t troll or harass and we address trolling and harassment when we see it because we can’t create together when we don’t all feel safe.