Microsoft Student Ambassador & ITBA

2026 still has time left, so maybe by the time I read this again a lot more will have happened. I wanted to write it now anyway, because it feels like a year where several things I'd been working on for a while started to pay off.

Getting into the Microsoft Student Ambassadors program was one of those goals I'd had for a while. There was no specific moment where I said "this is it". It was months of doing things that, from the outside, looked pretty repetitive: writing articles on Dev.to, keeping the blog in Spanish and English, publishing content about Microsoft technologies, checking stats, writing again.

Most of the time there was no sign that any of it was working. I just kept doing it.

When the confirmation email arrived, the first thing I did was show it to my family. I always end up sharing that kind of news with them before anyone else.

I was also selected for the second time in the ITBA program. This edition had 400 spots for over 11,000 applications.

The feeling was quite different from the first time. Not because it mattered less, but because I already knew the process and better understood what being there meant. The news found me much calmer.

Looking back, I think what I value most isn't having been selected twice, but having wanted to try again.

Most of the year also went into this portfolio. When I started I thought it was going to be another update. It ended up becoming a completely new project. I changed practically everything: the architecture, the design, the technologies, the way I write about projects, the blog, the bilingual support and even the way I present who I am.

There were screens I built multiple times. Components that disappeared after days of work. Ideas that looked good in Figma and didn't work at all in the browser.

In the end I realized the code was only part of it. What took the most time was deciding what to show and what to leave out. A portfolio talks about what you do, but it also says a lot about how you think. Finding that balance cost me much more than solving any technical problem.

I haven't defined what the next project will be. I do have a pretty clear idea of what kind of work I'd like to do. I'm interested in projects where the software ends up being used by real people, where there are interesting problems to solve and where I can keep learning while adding value to the team.

If you made it this far, thanks for reading. And if you think we could work together, reach out.