📜Values

Remote First

Communication is a challenge in the best circumstances, let alone in a remote and distributed team. It takes effort, do not underestimate it!

• Be transparent, clear and direct while remaining respectful.

  • Foster a safe environment to challenge each other and have meaningful debates.​

• Intentional collaboration – don't leave it up to chance. Know who to talk to, make the effort to get to know them and establish relationships. Make time to pair and chat.​

• Make yourself available when others need you.

  • When you're asked a question or to do something, own it – excel at it. Make sure you addressed their concern.​

• Make it easy to understand your work. It should follow our styleguides and established patterns. Split up your work in small increments. Pay attention to how others may perceive your writing and make it easy and fun to work with you.​

• Provide timely feedback to team members. In a remote setting, where body language cues are absent, help others understand how they come across. Take the opportunity to acknowledge their achievements, explain how their contributions are beneficial, and offer constructive guidance for improvement when necessary.

Keep It Simple

Simplicity is a key goal in design of our code, interactions and process. Unnecessary complexity should be avoided.

• Be pragmatic. Move fast when it makes sense. Don't spend all of your time working on Jira, PRs and Confluence when it's about a simple typo fix. Spend your time on meaningful work.

• While we want to have things written down, a 5 minute huddle is better than a lengthy email/comment exchange. Summarize your decision and share it transparently.​

• Make the right things easy – automate linters and other tooling to simplify code style discussions.​

• Ship in small increments – they're easier to review, test and reason about and give us an incremental business value.​

Focus on the Outcome​

We have a lot of power users internally and externally. Work with them, learn from them and work towards addressing their needs.​

• Understand why we're making changes​.

• Understand what is important to our customers​ and users.

• Understand how we're going to know if a change was good​.

• Use data (Sentry, Support Tickets, NewRelic, Sibyl) and real user feedback to prioritize.