Frontend developer · Lima, Peru

I own the outcome, from the first question to working software, directing AI across the build.

I've spent over a decade writing software. That experience guides how I use AI today. The projects below show what that looks like.

At a glance

years building software
16
personal projects built on my own
11
teams led, from 2 to 7 people
5
Selected work

Three projects, three ways of building

All projects
How I work

From the problem to working software

These are the decisions I pay most attention to.

  1. Start with what matters

    I focus the scope on the work that makes the biggest difference to the product.

  2. Understand before designing

    I understand the business and the problem before choosing how to structure the software.

  3. Code the team can read

    Clear names, small functions with one job each, and reuse of what is already there.

  4. Ownership through to production

    I take responsibility through to production. When a bug appears, I investigate the cause and fix it.

AI in my process

How I really use AI

I direct AI across design, code and review. I set the approach and decide what stays. Nothing ships until the tests, type checks and browser checks pass. If something fails, I investigate the cause before moving on.

See a full product I built this way: Pandacorp

AI does the work. I make the decisions.

Design: I set the direction, AI explores the options.
Code: AI writes, I decide how the pieces fit together.
Review: AI checks first, I make the final call.
The stack

The tools I build with

Frontend
ReactNext.jsTypeScriptTailwind CSSshadcn/uiReact Hook FormZodTanStack Query
AI in the build
Claude CodeCodexVercel AI SDK
Backend & data
Node.jsPrismaPostgreSQLFirebasebetter-auth
Quality & delivery
PlaywrightVitestSentryPostHogVercelDockerGitHub Actions

Got a problem worth solving?

That's the part I like best. Tell me what you're building.

Let's work together