About

Photo collage of David and family

A little bit about me, personally and professionally.

Short Version

I’m David — a senior frontend engineer with 10+ years building design systems, component libraries, and engineering workflows that help teams ship better software.

I’m bilingual (English/Spanish), which led me to create Se Habla Código — a YouTube channel and podcast dedicated to frontend development for Spanish-speaking developers worldwide. I also write regularly on my blog — covering everything from React and tooling to AI workflows and the occasional deep dive into hardware. Outside of code, I’m usually behind a camera or traveling with my family.

Longer Version

With over 10 years in the industry, I’ve worked across startups, agencies, and multinational organizations — building frontend systems that scale and leading the cross-functional work that makes them stick.

My background is an unusual mix: I studied both Systems Engineering and Law, which gives me a distinct lens on structure, risk, and the kind of governance that actually matters in high-stakes environments. I’ve spent a significant part of my career in FinTech and HCM products where GDPR, PCI, and SOC2 aren’t checkboxes — they’re engineering constraints you design around from day one.

On sharing and teaching: Since 2019, I’ve invested in giving back through content. Se Habla Código started as a way to bridge the knowledge gap for Spanish-speaking developers, and it’s grown into something I’m genuinely proud of — deep dives on frontend architecture, real-world tutorials, and honest conversations about the craft. I also write on my blog whenever I run into something worth sharing.

This same instinct carries into my day-to-day work. I mentor engineers by helping them sharpen their workflows, identify design patterns that lead to robust solutions, and adopt best practices that stick — through code reviews, mini tutorials, and documentation that actually gets read. Teaching has made me a sharper engineer; explaining something clearly forces you to actually understand it.

On AI: AI is now a core part of how I work — from building components and full feature flows to code review, legacy code analysis, and research. I use it to move faster and think more clearly, not as a substitute for engineering judgment.

Beyond the screen: When I’m not coding, I’m usually traveling with my family or behind a camera lens. I think the perspective you gain from slowing down and observing the world makes you a more thoughtful engineer — and a better collaborator.