Frontend
Interfaces people actually use
- React
- TypeScript
- JavaScript
- Next.js
- Tailwind CSS
- Framer Motion
- GSAP
- Vite
about me
I build production software end to end — the interface a customer touches, the API behind it, and the infrastructure that keeps it fast. Most of my work lives where product commerce and engineering meet: subscription platforms, Shopify apps, multi-vendor marketplaces and AI-assisted tooling.
My default is boring, typed, observable systems with a carefully crafted surface on top. I care about the first paint, the empty state, the error message and the invoice at the end of the month — because those are the parts users and founders actually feel.
Right now I'm shipping edge-first architecture and AI automation into products that need to stay cheap at scale.
quick facts
Scope is a design tool. I release the version that answers the user's question, then earn every extra layer of complexity with evidence.
Cloudflare Workers, caching and streaming push work closer to people. Latency is a product feature, not an infra footnote.
TypeScript at every seam, validation at every entry point. Most production incidents are just untyped assumptions growing up.
Automations need fallbacks, budgets and review paths. A model is a fallible dependency I design guardrails around.
These are the technologies I reach for when something has to run in production — not a wishlist. Grouped by the part of the product they hold up.
Interfaces people actually use
APIs that stay boring
Stores and storefront apps
Edge-first delivery
Schemas before code
Assistants that do real work
Oracle
Core cloud architecture, identity, networking and managed services on OCI.
Oracle
Applied generative AI: retrieval, embeddings, prompt design and deployment patterns.