# Our values
Apliteni was founded with a mission to provide a comfortable workplace for passionate people whose eager to discover and growth.
- We prefer asynchronous communication.
- We don't expect immediate answer.
- We use online meetings as a last resort.
- We defend everyone's right for uninterrupted, deep work.
- You have the right to make any decisions yourself if you've considered several points:
- You asked for your colleagues' point of view.
- You told the lead of your team about the holiday.
- You are acting in the interests of the company.
- We prefer open Slack channels. Private channels are only for personal communication.
- We use this handbook to show how our company works from the inside.
- We frankly criticize, if we disagree, but we criticize correctly.
- We document and provide open access to:
- OKR for long term goals and results.
- User Story Maps to plan the development process.
- RFC to develop features and iterations.
- Jira for stories.
- Reveal our company's financial reports on our Google Drive monthly.
- We write frankly about the advantages and current disadvantages of the company:
- We are kind and polite to our colleagues and to our customers, we are thanking for the help.
- We prioritize helping colleagues in case they have any difficulties.
- We have demo-days, educational webinars and checkpoints to sync inside the team.
- Code review is the opportunity to improve our own skills and share our experience with colleagues.
- We are kind and polite to our colleagues and our users.
- We give negative feedback and personal critics in a 1:1 format.
- We talk about others only things that we could say them personally.
- Only the results matter. We do not track working hours neither we require constant presence at the workplace. (The customer support team has their own shedule).
- We prefer to show results step by step, without blocking on an issue for a long time. Each iteration has its value for the customer.
- We contribute to open source projects.
- We the smallest thing possible and get it out as quickly as possible.
- We write RFC first before doing something significent.
- We make small merge requests. Make it easier for your colleagues to perform code reviews.
- Everything is in draft. Everithing is a subject for change.
- We are digging deeper into the matter (opens new window).
- We are asking questions before the development:
- How will the customer benefit from this?
- What are customer's goals?
- Do we understand everything? Is there anything we need to clarify and research?
- We treat our mistakes as inevitable. We eliminate them, draw the right conclusions and move on.
- We are all responsible for our failures and bugs. We build on the fact that each of us has good intentions and we have done everything possible for the good of the company.
- We don't associate ourselves with the written code (opens new window). Code Review is the way to learn something new.
# What influenced us
- "No Rules Rules: Netflix and the Culture of Reinvention" by Reed Hasting w/ Erin Meyer.
- "Multipliers: How the Best Leaders Make Everyone Smarter" by Liz Wiseman and Greg McKeown.