About

I work at the intersection of earth science and software architecture. By day, I process GNSS data and build headless automation pipelines for geohazard assessments. Outside of that, I design full-stack applications and local-first systems for startups and freelance clients.

My engineering philosophy is entirely driven by frustration and constraints. I don't care about the newest framework; I care about building resilient, offline-capable systems that actually solve the problem at hand. Whether that is a B2B lab marketplace, a deterministic constraint engine for math worksheets, or a geoprocessing pipeline, the goal is always the same: low overhead, high utility, and architecture that doesn't collapse under its own weight.

This blog is where I document the reality of building those systems. We are in an era of software where tools increasingly promise to think for us, making the gap between an idea and a prototype feel deceptively tiny. But tools don't democratize outcomes, and they don't replace the need for deep domain context.

I write here to force myself to navigate the execution gap. To interrogate the technologies I use, separate the hype from the practical leverage, and document the architectural decisions that happen when you actually have to deploy and maintain a system in the real world.

If you want to read someone working through the friction of turning intent into lasting infrastructure—welcome.