Why I built this site!

I’ve been building software for more than fourteen years, and I’m still the person who gets excited when a new framework drops, a browser ships a new API, or a build gets a few seconds faster. I like knowing how things work under the hood, and I like the moment when a hard problem finally clicks.

What I haven’t done is write much of it down. This site is my fix for that.

A career worth writing about

My path has taken me through very different engineering cultures, each with its own way of building:

• Intel, where I started out building internal applications. I learned CI/CD, test-driven development, and what it takes to lead a team of developers and teach new technologies to others.
• Amazon, where I worked on seller and partner support platforms, and later AWS Marketplace, designing large-scale distributed services.
• Microsoft, where I built address bar features for Microsoft Edge, and today lead Finance and Sports experiences across Bing, Copilot, and MSN in the Microsoft AI organization.

Along the way I moved from Costa Rica to Vancouver, went from Angular and .NET to React and TypeScript, and from on-prem servers to the cloud. Each step taught me something I wish I’d had in writing before I started it. That’s the kind of thing I want to share here.

What I’ll write about

• The craft of front-end engineering. React and TypeScript architecture, reusable components, and the details that make an interface feel fast and solid.
• Data visualization. How to turn numbers into something people actually understand, especially in finance and sports, where I spend my days.
• Accessibility. Building interfaces that work for everyone isn’t a checklist at the end; it’s part of the craft from the start.
• Lessons from big companies. How different teams approach design reviews, on-call, testing, and shipping at scale, and what I’d take from each.
• New tech I’m trying. Tools, frameworks, and AI-assisted development, with honest notes on what works and what doesn’t.

Learning by writing

The biggest reason is selfish: writing is how I learn. Explaining something clearly forces me to understand it properly. The gaps I can hide in my head show up immediately on the page. If a post helps someone else along the way, that’s the best possible bonus.

I’m also bilingual, and I hope to write some posts in Spanish. Plenty of great engineers in Latin America are looking for content in their own language, and I’d like to contribute to that.

Let’s connect

If something here is useful, or you think I got something wrong, I’d love to hear about it. You can find me on LinkedIn and GitHub.

Thanks for reading. More soon.