Judgment over code.
Knowing what NOT to build is more valuable than knowing how. Most of the work is editing the brief, not the file.
Over a decade shipping on the web — and I'm still on it. Long enough to have opinions formed in production, not so long that the work has stopped being interesting.
Most of those years went into product teams: web platforms, native apps, the messy seams in between. The same thing keeps mattering across every project — pick the small number of decisions that actually move the product, get those right, and don't be precious about the rest.
Today I work as an independent contractor. Most engagements are long-term, fully remote, full-stack: a founder or product team that needs a senior pair of hands to take an idea from Figma to App Store without four other people in the loop.
Lately I've been deep in AI-augmented products — RAG, embeddings, LLM integrations on top of existing apps. Same craft as before; only the runtime got more interesting.
Knowing what NOT to build is more valuable than knowing how. Most of the work is editing the brief, not the file.
A few stacks I can ship in my sleep, instead of a buzzword salad. React, React Native, TypeScript, Postgres — and the LLMs sitting on top of them.
From SQL schema to button radius. One person across the stack means fewer handoffs and a tighter feedback loop with whoever pays the invoice.
Decks, repos, PRs and Slack — written like a person, not a contractor billing hours. If a stakeholder needs a translator to read me, I failed.
Developed scalable websites using Gatsby/Next.js and various content managers. Created bridge applications with React Native.
Developed and maintained a YouTube-connected app for managing and withdrawing earnings, deployed to iOS App Store with notification handling.
Developed interfaces in React Native for iOS and Android. Maintained backend modules in Nest.js with Postgres.
Participated in architecture meetings to redesign the website platform for Diario El Universo.
Created reusable components for React Native and wrote unit tests for quality assurance.
Built frontend features for transcription and annotation platforms.
Led new customer implementations and code revisions. Made technical decisions to enhance product quality.
Developed new user-facing features using React.js. Built reusable components and optimized them for maximum performance.
Designed and maintained new website features. Made architecture decisions for new developments.
More than a decade shipping product across web, mobile and AI left me something more valuable than a stack: judgment. If your team is stuck on a technical decision, evaluating a stack, or wants a second opinion before sinking months into a direction — let's talk.