Behaviour and protocol

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


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 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 Purchasing licenses and memberships Sharing sensitive information Stack and services Wordpress

Tools and services

Stack and services

Or Ab-stack-tion! 🤦‍♂️

This document lists the tools and services that we use on our projects.

Finding a balance between trying out something new 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?

Programming languages

  • JavaScript (TypeScript)
  • Ruby
  • C#

Managing DBs and runtimes

  • asdf to easily install the required runtimes for most of our projects
  • docker-compose to easily get the DBs started - using the right versions

.NET has its own built-in SDK manager.


Web apps


* WordPress has its own guideline as it’s a whole separate ecosystem

Mobile apps






We have a three-color system, for keeping track of the services we’ve used and our experience with using them.

  • 🟢 These services have been widely used at Abtion, and they usually provide the necessary functionality that we expect from them.
  • 🟡 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.
  • 🔴 These services have been used or analyzed, and they do not live up to Abtion standard.

Use the 🟢 services unless there’s a good reason not to. If there is a 🔴 service that the team wants to use the team must first check with the Principal Engineer or CTO.




  • 🟢 Through the chosen PaaS (Heroku / Scalingo)
  • 🟡 Or GitHub Actions (for the more peculiar projects)


  • 🟢 Rollbar
  • 🟢 Librato
  • 🟢 Papertrail
  • 🟡 New Relic. In Heroku: use the addon.
  • 🔴 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.


  • 🟢 Mailtrap for staging/review-apps.
  • 🟢 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

DNS management

Sending and receiving SMS