Behaviour and protocol

Code Code reviews Consulting 101 Feedback Good meetings practices How to facilitate team meetings Inclusive language Values

Career

360 review Continuing education policy Engineering manager career ladder Roles Software engineer progression framework Technical skills sheet

Employee manual

Abtion's pomodoro Employee benefits Internal days & community Intro Parental leave policy Safety and security Schedule, time tracking & calendar Sickness & unplanned absence Travelling Vacation & planned time off Work from anywhere policy

Project management

Technical setup when starting a new project Client discontinuing hosting or sla Converting projects from development to maintenance mode Estimating Go live checklist Handoffs Invoicing guidelines Procedure for traffic Sla

Setup

Audio setup Create amazon bucket Database backup setup Gpg signing Pairing setup

Technical practices

Bug triaging Css How and why we do design research Kick off meeting Pair programming Tdd testdriven development Workflow

Templates

Readme.standard

Tools and services

Access and permissions Purchasing licenses and memberships Sharing sensitive information Stack and services Wordpress
=

Tools and services

1password

All credentials and sensitive information used by a team must be hosted on 1password. See Access and Permissions for more on how we organize vaults. Note that external members can be invited to the vault. It is common to share a vault with a client’s team. If someone from Abtion needs access to information stored in the vault, the person should request access to the vault.

Abtion’s best-kept secret

When we need to share sensitive information with someone who is not part of 1password, we use secret.abtion.com. There, we can put any text and generate a safe link that can only be seen once and expires in 24 hours if it’s not opened in that time. Note that we need to inform the client on how the webpage works. Remember to ask the receiver to store the shared information safely.