I’ve always been interested in systems and understanding how things work.
I grew up surrounded by cables, amplifiers, and computers. My father worked in the music industry and later opened a computer academy and a computer store at a time when very few people had a computer at home. Between records, hardware components, and CRT monitors, I learned early on how to install operating systems, assemble PCs, deal with viruses, or spend hours copying code from magazines to make games work.
Over time, I studied computer science and started working in software development. I’ve gone through different stages and technologies: desktop applications, backend development, automation, distributed systems, cloud infrastructure, and on-premise environments. For many years I worked mainly as a developer, but gradually I moved closer to the world of DevOps and platform engineering, drawn to the less visible side of systems and to understanding how all the different pieces connect together.
Today, I especially enjoy automating processes, simplifying operations, and building tools that make life a little easier for other teams. I usually work with infrastructure, CI/CD, observability, and automation using technologies such as Python, Terraform, Ansible, and Kubernetes, although I’ve become less interested in chasing every new technology simply because it’s new.
Over the years, I’ve also come to appreciate less technical aspects of the job: clear documentation, autonomy, continuous learning, and the importance of building things sustainably over the long term — both for the systems themselves and for the people maintaining them.
Outside of work, I’m interested in topics related to learning, health, and human performance. Probably because, after many years in technology, I’ve become increasingly interested not only in how systems work, but also in how we work as people.