Memories

I still remember the first time I used Ansible. It felt like magic. Writing a few lines of YAML and watching systems fall into place gave me a sense of efficiency I had never experienced before. It was like getting a superpower, suddenly I could automate tasks across dozens of servers, enforce consistency and reduce human errors.

It was one of those moments in tech where something just clicks. That experience stuck with me. It shaped the way I think about managing infrastructure. Since then, I’ve worked with a range of tools. Each one brought something unique to the table. I learned something from all of them.

But after a while, patterns emerged. Certain things kept repeating - workarounds, orchestration logic or glue code. I started to feel like I was bending the tools to fit how I wanted to work, instead of the other way around.

That’s when the idea of building my own tool started to form. Not because the existing ones were bad, far from it. But because I wanted something that brought together the pieces I valued most.

This post is the first in a series where I’ll talk a bit about what I’m building and why. Just sharing my thoughts and the ideas behind it.

More soon.