Del Rey
Valmoria.

Self-taught, based in the Philippines, working remotely. I came into software from operations work, which is why my projects tend to start at the process rather than the framework. The published portfolio covers catalog enrichment, branch audits, inventory, intake, payments reconciliation, speech-to-text and interactive web work — 18 documents, several of which cover different components or stages of the same system.

I write the decision down before I write the code: which steps are deterministic, which need interpretation, where a person has to approve, and what happens when a step fails. Then I build against acceptance statements somebody can test without me in the room. The habit comes from running my own systems in production — including this website, which sits on a self-hosted Docker stack behind a Cloudflare tunnel and reports its degraded states instead of hiding them.

n8n and custom Node services for workflow; PostgreSQL and NocoDB for records; React, Vite and Three.js on the front end; Docker and Cloudflare for delivery; Gemini and Whisper where language or speech genuinely needs interpreting; Keycloak when access control has to be real. I choose self-hosted open source when it removes a recurring licence cost the project would otherwise carry forever.

Every figure on this site is a measurement from something that ran: 243,000 SKUs enriched with no language model in the request path, 267 recorded n8n executions, a branch audit rolled out across 64 branches, 32 workflows of which 14 were validated end to end. Where a number was not measured, it is absent. Where a system is degraded, the interface says so. That is the same standard I bring to a client report.