I build fast, boring, reliable web systems — and make them feel considered.
Reliable systems 
that feel considered.
Rebuilt the invoicing dashboard for a B2B billing product so finance teams stopped exporting to spreadsheets.
Decision
Kept the reporting queries in Postgres with three materialized views refreshed on write, instead of adding a separate analytics store. One database to operate, and the numbers on screen are always the numbers in the ledger.
An offline-first data-collection app for survey teams working without reliable signal.
Decision
Chose last-write-wins per field, not per record, with a visible conflict log. CRDTs were on the table; per-field merges covered every real conflict we saw in two months of pilot data, at a tenth of the code.
A webhook delivery service with retries, signing, and a replay console for customer support.
Decision
Stored every attempt as an append-only row and built the replay console on top of it. Support could answer "did you send it?" themselves, which removed most of the tickets that reached engineering.
Ledgerline launched on plain Postgres views in two weeks; the clever caching layer it was meant to replace never got built.
One query plan showed a missing index behind 80% of Ledgerline's latency — a one-line fix instead of a new service.
Relay's replay console and runbook let support close delivery tickets without paging an engineer.
| Group | Instruments | Qty |
|---|---|---|
| Languages | TypeScript · JavaScript · SQL · Python | 04 |
| Runtime | Node.js · React · Next.js · Astro | 04 |
| Data | PostgreSQL · Redis · MongoDB | 03 |
| Infra | Docker · AWS · Cloudflare · GitHub Actions | 04 |
| Tools | Git · Vitest · Playwright · Figma | 04 |
Email is the fastest way to reach me. Tell me what you are building and where it hurts.
Replies within two working days