Alfie Pelicano

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.

Featured Projects

Earth science automation, civic platforms, and algorithmic tools — built to make hard things tractable

💻 Platforms & Production Work

🔬
In Production

PipetGo

B2B laboratory marketplace MVP connecting businesses with ISO-accredited testing labs, with multi-tiered pricing and role-based authorization workflows.

Problem: Businesses had no centralized source for accredited labs — data was scattered, outdated, and often missing accreditation details.
Solution: A searchable marketplace with three pricing modes (QUOTE_REQUIRED, FIXED, HYBRID), multi-role authorization, and RFQ workflows connecting certified labs and clients directly.
Stage: MVP undergoing User Acceptance Testing with initial partner organizations before pilot deployment.
V2 rewrite: V1 shipped and exposed three conflicting schema sources and an unenforced tenancy boundary; V2 is a ground-up rewrite on a single authoritative schema with tenancy enforced at the data layer.
Next.js 14 TypeScript Prisma NextAuth Zod Vitest
🎨
In Production

ArtPortfolio

High-performance statically generated Astro CMS built over a weekend — optimized for minimal cognitive load and fast asset delivery for digital art commissions.

Problem: Existing digital art commission sites were slow, cognitively noisy, or required ongoing CMS subscriptions — not practical for a solo artist portfolio.
Solution: Statically generated Astro site with zero client-side JS by default, optimized image delivery, and a content structure designed to minimize decision fatigue for commissioners.
Impact: In production as a live art commission site — fast, cost-free to host, and maintainable without a CMS subscription.
Astro Static Site Generation GitHub Pages

🌋 Earth Science & Field Automation

🛰️
Active Development

MOVE Faults

Flagship GNSS automation monorepo replacing decades of fragmented legacy scripts with a modern distributed processing stack.

Problem: Decades of fragmented MS-DOS/Bash GNSS processing scripts with no orchestration, no fault tolerance, and no field-usable interface.
Solution: Celery-backed distributed task queue, real-time NMEA TCP streaming, and an offline-capable React field app for live fault monitoring operations.
Stage: Active development — core task queue and streaming pipeline operational; field app in integration testing.
Python Celery Redis React FastAPI Docker
🌋
Active Development

EIL Hazard Suite

Decoupled geohazard system: a headless spatial processing engine for landslide susceptibility paired with a React-based ground-truth validator.

Problem: Geohazard susceptibility analysis required manual, error-prone GIS desktop workflows with no programmatic access or field validation tooling.
Solution: EIL-Calc: headless spatial processing engine for landslide susceptibility scoring. EIL-Viz: React visualizer for overlaying and validating results against ground-truth field data.
Stage: Active development — EIL-Calc processing pipeline stable; EIL-Viz in active integration.
Python FastAPI React Spatial Analysis

🧰 Also Built

  • HAR Automation Pipeline Python pipeline automating PHIVOLCS Hazard Assessment Report generation from multi-format OHAS data.
  • Drive Archaeologist Python CLI for excavating and normalizing legacy GNSS data off drives with inconsistent structure.
  • PHAST Chrome extension injecting GIS controls into Leaflet maps and generating official PHIVOLCS hazard text.
  • Window Cards Generator Zero-dependency constraint solver that generates printable math drill grids — the first thing I built that other people used daily.
  • SIPAT Open-source offline-first CAPI survey tool for field researchers.
  • YAKAP-Link Offline-first medicine inventory and redistribution system for Philippine rural health units.
  • ISPHDB Local network monitor that separates LAN bottlenecks from gateway and upstream ISP failures.
  • UGT (Chaotic Circuits) Python/LaTeX reconstruction of a 2004 undergraduate physics thesis — Lyapunov exponents and bifurcation solvers.
  • Washboard Car wash queue and booking system replacing pen-and-paper operations with QR check-in.
  • ProseProxy Self-hosted headless-browser proxy that extracts readable content from ad-heavy web novel platforms.
  • Homebase Multi-residence household command center built around ADHD executive-function support.

Technical Skills

Frontend

  • Next.js 14 (App Router)
  • React 19 (Server Components)
  • Astro (Static Site Generation)
  • React / Vite
  • TypeScript
  • Vanilla JavaScript
  • Tailwind CSS
  • shadcn/ui

Backend

  • Python / FastAPI
  • Node.js / Express
  • Next.js API Routes
  • Celery (Distributed Task Queues)
  • Redis
  • Docker
  • Agentic AI Workflows (LangGraph / Ollama)
  • Prisma ORM
  • NextAuth.js / Passport.js
  • Zod Validation

Database & Infrastructure

  • PostgreSQL (Advanced SQL)
  • Neon (Serverless)
  • Supabase (PostgreSQL)

Python & Automation

  • Python 3.11+
  • Click CLI / Rich Terminal
  • Pandas (Data Processing)
  • NumPy / SciPy
  • Pytest (Testing)
  • Shell Scripting

Domain Expertise

  • GNSS Processing & Field Ops
  • Spatial Geohazards (Landslide / Seismic)
  • Heuristic Engines & Constraint Solving
  • Scientific Computing & HPC
  • Fortran (Legacy Scientific Code)

Testing & Quality

  • Playwright (E2E)
  • Vitest (Unit)
  • Pytest (Python)
  • Git Workflows

Tools & Workflows

  • Agentic Workflow Design & Orchestration
  • LaTeX / Beamer
  • ADR-driven Architecture
  • Linux / Bash

About Me

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.

Let's Connect

Building something interesting? Need a developer who actually ships?
Let's talk.