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

Technical practices

Bug triaging

To remedy bugs, we have a certain procedure that we encourage you to follow.

How to report bugs

  1. Find a bug.
  2. Ensure that the bug has not already been reported in Asana.
  3. Check if the bug is still valid and reproducible.
  4. Add an Asana card to the correct project:
    • Add a description of the bug and how it can be reproduced.
    • Add images to the task if applicable.
  5. Prioritize the bug based on its severity.
    • If it is not severe then add it to the backlog and assign it to the project manager.
    • If it is severe, put it in the top of the backlog.

How to fix bugs

  1. Pick a bug from Asana.
  2. Write a failing test or figure out why existing tests did not fail.
  3. Make the test pass.

Tools for preventing bugs

Recommended tools for catching bugs are:

Code needs to be test-driven and written in pairs. This is the Abtion way and has proven to minimize bugs.

Additional reading