My README

Hey there! I'm Ernesto 👋 If you're here, we might work together. This is your guide to how I operate—what drives me, how I think, and what you can expect.

What drives me?

Building systems that multiply team velocity

The work I'm most proud of isn't solving one problem—it's creating abstractions that make entire teams faster. At Dispel, I built form libraries, component systems, and architectural patterns that turned multi-day tasks into hours. When something I build removes friction for multiple developers, that's the multiplier effect I'm after.

Staying ahead of the curve

I'm always experimenting with emerging tech—especially AI tooling—to see how it can improve our workflows and solve complex problems. But I only adopt what adds real value. I've learned that being forward-thinking means knowing when to push for better tools and when to stick with what works.

Caring deeply about craft and details

I don't just make things work—I make them feel right. Whether it's a form interaction, an email template, or a component API, I'm meticulous about the details because I believe great UX and solid engineering aren't separate concerns. Thoughtful design and clean code compound into products people actually enjoy using.

Making collaboration easy and productive

I believe the best work happens when it's easy to work together. I'm responsive (even under pressure), approach every conversation with good intent, and genuinely enjoy collaborating with product and design. I give thoughtful PR reviews, help teammates debug tricky issues, and try to make showing up to work a little more enjoyable.

How I work?

I break big problems into smaller pieces

Complex features become manageable when you chunk them into clear, reviewable increments. I've learned this makes development smoother, PRs faster, and delivery more predictable. It's a simple habit that compounds over time.

I write to clarify my thinking

Writing forces me to find gaps in my logic. Whether it's documentation, architectural proposals, or code comments, externalizing my thoughts helps me (and others) grasp complex systems faster. I also lean on diagrams when visual models make things clearer.

I default to good intent

When someone questions my approach or suggests something different, I assume they're trying to make things better. I ask questions to understand their reasoning, not to defend my position. I hope you'll do the same with me.

I'm always willing to help

Whether it's answering questions, reviewing code, brainstorming solutions, or mentoring teammates, I make myself available. Great teams push each other forward, and I believe being supportive and approachable is part of what makes engineering work actually work.

I change my mind when convinced

I care more about making the right decision than being right. If you bring better reasoning or a clearer path forward, I'll happily change direction. Low ego, high conviction—until something better shows up.

A few things about me:

  • 13 years building web platforms—from my first project (a website for my local movie theater in Imperial, CA) to enterprise SaaS
  • Front-end specialist with full-stack capabilities (React, TypeScript, Next.js, Node.js)
  • Based in Flagstaff, AZ—a beautiful mountain town I love calling home
  • Remote work advocate—it lets me be more present with my family while staying productive
  • When I'm in flow state, I code to music or podcasts (Joe Rogan, Nick Bare, Syntax)
  • Outside of code: I'm passionate about cooking (culinary school is on my bucket list!), photography, and drawing
  • Big on psychology and wellness—Rick Rubin's The Creative Act: A Way of Being is a favorite
  • Cold brews and iced matchas keep me going
  • When I'm not coding, you'll find me running, cycling on my Trek Domane, or spending time with my family