PipetGo
B2B laboratory marketplace MVP connecting businesses with ISO-accredited testing labs, with multi-tiered pricing and role-based authorization workflows.
Research Specialist & Geodetic Software Developer
Where tectonic data meets tractable software
"All models are wrong, but some are useful." — George E. P. Box
I process GNSS and geophysical data at PHIVOLCS 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.
Earth science automation, civic platforms, and algorithmic tools — built to make hard things tractable
B2B laboratory marketplace MVP connecting businesses with ISO-accredited testing labs, with multi-tiered pricing and role-based authorization workflows.
High-performance statically generated Astro CMS built over a weekend — optimized for minimal cognitive load and fast asset delivery for digital art commissions.
Flagship GNSS automation monorepo replacing decades of fragmented legacy scripts with a modern distributed processing stack.
Decoupled geohazard system: a headless spatial processing engine for landslide susceptibility paired with a React-based ground-truth validator.
I work at PHIVOLCS processing GNSS and geophysical data for earthquake research and fault monitoring, and I write the software that replaces the manual parts. The two roles aren’t separate: sixteen years of scientific computing taught me that precision, edge-case handling, and long-term maintainability aren’t engineering virtues, they’re survival requirements when your data tracks how the ground moves.
Lately that sits alongside contract platform engineering — CI/CD, cloud deployment, and release gating for production systems. Different domain, same instinct: I’ve gotten suspicious of architectures I can’t still understand six months later. No moonshot hype, no blockchain detours.
In practice that means I write the test first when a bug is subtle, and skip it entirely when I’m still sketching. I keep READMEs a stranger could follow, on the theory that in six months I am the stranger. And I ship the boring version before finding out whether anyone wanted the interesting one.
Outside work I’m usually helping my kids with homework, or automating something that didn’t need automating.
Building something interesting? Need a developer who actually ships?
Let's talk.