Atanas Alexandrov

A lot of projects seem to fail, not due to the code, but due to the absence of a quality-mindset in its entirety, where an engineer such as myself steps in to fix problems.

When there is no foundation of quality, a mountain of things accumulates. The ever growing technical debt, increasing number of bugs and lengthy delivery times quickly become a mess. My approach is to establish quality building blocks within the architecture, and advocating for test-driven development from the start, in addition to well defined quality check points. This will ultimately turn things around and accelerate development speed and resilience of the systems.

In projects Ive been a part of, Ive successfully driven test-coverage from zero to over 80 percent. I have also successfully stabilized the CI/CD pipelines allowing teams to release software into production with confidence. The increase in reliability seemingly contributes to positive outcomes.

My roles appear to blend those of the developer, DevOps engineer, and architect. Bringing along with it a strong proficiency in Go, AWS, and Terraform, coupled with the intention of sustainable software quality and architecture, from automated builds and tests to production ready cloud infrastructure.

It is my aim to build resilient systems and teams, which remain functional in the long run, as opposed to merely functional. Whilst others might prioritize immediate solutions, sustainable qualities appear to have the most enduring effect, albeit on a more long term scale.