Behaviour and protocol

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


360 review 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 Estimating project maintenance Go live checklist Handoffs Invoicing guidelines Procedure for traffic


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



Tools and services

Access and permissions Preferred services Purchasing licenses and memberships Sharing sensitive information Stack guideline

Tools and services

Preferred Services

Finding a balance between trying out a new service or using a well-known tool is tricky. There are several things to consider: can a tool that we previously used solve the problem? Is the learning curve of the new tool justified by the gained efficiency? Is the new (or old tool) GDPR compliant? As the matter is tricky, simply listing previously used tools is not enough. Instead, we have a three-color system.

  • Green list: These services have been widely used at Abtion, and they usually provide the necessary functionality that we expect from them. If there is a service in this category, but the team wants to use a different one, the team must first check with the Principal Engineer or CTO.
  • Yellow list: We’ve used the services before, and we are satisfied. The services in this list should be considered before the team decides to use a different tool.
  • Red list: The services in this list have been used or analyzed, and they do not live up to Abtion standard. A team must request permission from the Principal Engineer or CTO before using this tool on a production system.

Evaluated services

DNS management

Cloudflare Use dns-configuration to manage the configuration.

Sending and receiving SMS


Error management

Rollbar In Heroku: use the addon. Default configuration on Muffi Rails.

Sentry In Heroku: use the addon. Avoid on small projects as it is cumbersome to set up to notify in Application Service when the project goes into maintenance.


SendInBlue: You’ll need to manually create a project account. Default configuration on Muffi Rails. Remember to set up DKIM.

SendGrid Countless issues when using the addon on Heroku. Accounts are banned on regular basis.

MailGun Countless issues when using the addon on Heroku. Accounts are banned on regular basis.

Mail testing

Use mail-tester to test mail setup.


Use Mailtrap for staging/review-apps.

Log management

Papertrail. In Heroku: use the addon.

In-memory data store

Heroku Redis. Green for all apps hosted in Heroku.

Performance monitoring

New Relic. In Heroku: use the addon.


The app I’m working on is using a red service. Should I switch to a recommended service? The app should change to a yellow or green alternative. If there are no alternatives, the maintenance team will continue with the service and check in the next maintenance window.

Apps should change services on active development (if it has been already budgeted on that round), or in the next maintenance window.