Research Specialist · Contract Platform Engineer 📍 Quezon City, Philippines
"All models are wrong, but some are useful." — George E. P. Box
I process GNSS and geophysical data for earthquake research and fault monitoring. Most of what I build exists because some part of that work was still being done by hand — a folder of MS-DOS-era scripts, a spreadsheet passed around by email, a form somebody retypes every week.
Sixteen years of that, lately alongside contract platform engineering. I've gotten suspicious of architectures I can't still understand six months later.
- Languages: Python, TypeScript, SQL, Bash, Vanilla JS
- Architecture: Next.js, Astro, React/Vite, PostgreSQL, NeonDB
- Backend & Automation: Celery, Redis, Docker, FastAPI, agentic AI workflows
- Infrastructure: Google Cloud Run, GitHub Actions, Secret Manager
- Domain: GNSS processing, spatial geohazards, heuristic engines, constraint solving
-
PipetGo — B2B marketplace connecting businesses with ISO-accredited testing labs. Multi-tiered pricing and role-based authorization. V1 shipped, then showed me three conflicting schema sources and a tenancy boundary nothing actually enforced; V2 is the rewrite on one authoritative schema with tenancy enforced at the data layer.
-
MOVE Faults — GNSS automation monorepo replacing decades of fragmented scripts. Celery-backed distributed task queue, real-time NMEA TCP streaming, and an offline-capable React field app.
-
EIL Hazard Suite — Decoupled geohazard system: EIL-Calc, a headless spatial engine for landslide susceptibility scoring, and EIL-Viz, a React visualizer for checking results against ground-truth field data.
-
ArtPortfolio — Statically generated Astro CMS, built over a weekend to replace my daughter's art commission site. Fast asset delivery, nothing to learn before posting.
HAR Automation · Drive Archaeologist · PHAST · WindowCards · SIPAT · YAKAP-Link · ISPHDB · UGT · Washboard · ProseProxy · Homebase