Microsoft Student Ambassador & ITBA

2026 is still happening as I write this. But there's already enough to say it's been the year several things I'd been building for a long time finally arrived.

Getting into the Microsoft Student Ambassadors program was something I actively pursued for months. Publishing on Dev.to, keeping the bilingual blog active, creating technical content with links to Microsoft resources, constantly tracking the visitor counter. There were some pretty boring weeks doing that. It wasn't inspiring or cinematic. It was consistency.

When the confirmation came I shared it with my family. I always experience these moments like that, with the people who know what it took.

Being selected at ITBA for the second time, this time among 400 spots nationwide, felt calmer than the first. Not because it mattered less, but because I already knew what it meant. I'd been through that process before, I knew what was coming and I knew I could do it.

Selected twice. Two different processes. The same conviction that it's worth preparing well.

V3 was the most demanding project I've taken on alone. Next.js 15, React 19, Tailwind v4, Framer Motion, Supabase, integrated AI, bilingual from the design stage, with real case studies and a custom blog system. There were long nights, decisions I remade three times and parts of the design I scrapped completely before finding something I was happy with.

What took the most time wasn't the code but deciding what to say and how. A portfolio is strange because it's technical and personal at the same time. You have to show you know how to do things but also who you are. That doesn't have a clear solution.

I'm looking for the next big project. I'm not in a rush but I do have standards. I want something where the problem is real, where what I build actually gets used and where I can apply everything I've been building up over these years. If you're reading this and think we could work together, you can find me here.