13 Nov 2025
If you're reading this, welcome to my corner of the internet where I document everything I'm learning about DevOps, cloud infrastructure, and software development.
Let me tell you a bit about how I got here.
I studied Electronic Engineering in Argentina, which gave me a solid technical foundation but didn't quite prepare me for where my career would actually take me. After graduating, I joined a multinational company where I did a bit of everything, learning on the fly, solving problems, and discovering that I really enjoyed the technical side of making systems work.
Eventually, I moved to the Government of Santa Fe, where my real learning journey began. I started in Level 1 technical support the classic "have you tried turning it off and on again?" role. But I was curious, and every ticket was an opportunity to learn something new.
Slowly, I started picking up:
If you want more details about my background, check out the About section.
The turning point came when I got involved in a large government project from start to finish. At first, I was just building a CRUD application, nothing fancy, just forms and databases. But then something clicked.
I realized the interesting part wasn't just writing code, it was everything around it:
That's when I discovered DevOps, and honestly, I haven't looked back.
I moved from pure development to managing the entire infrastructure, administering servers, deploying code to testing environments, pushing to production, and making sure everything stayed running smoothly.
In August 2024, I moved to Italy with my family, a big change that gave me even more motivation to focus on my career transition into DevOps. Since early this year, I've been diving deep into modern DevOps practices:
I built this website using Laravel and deployed it on a virtual machine in Oracle Cloud's free tier (because free is good, and learning cloud deployment is better).
This blog serves three purposes:
1. For you: If my step-by-step tutorials and explanations help someone else learn, that's fantastic. I remember struggling with concepts that seemed obvious to everyone else, so I try to explain things clearly.
2. For me: Documentation is my second brain. When I need to remember how I configured something three months ago, I can come back here instead of Googling for the third time.
3. For learning: There's something about explaining a concept that forces you to truly understand it. Writing these posts helps me solidify everything I learn.
I also share these posts on LinkedIn to connect with other people learning similar things and to hopefully start conversations with folks working in the field.
I'll be posting about:
The posts won't be perfect. Sometimes I'll make mistakes (and probably document those too). But they'll be honest, practical, and hopefully useful.
I'm always happy to chat with other people learning DevOps or working in the field. You can find me on:
Thanks for stopping by. Let's learn together.