Software Engineer.
Tools with a pulse.

The four surfaces all route through one edge middleware: it reads the Host header, classifies the request, and rewrites into the right App Router segment.

Bookings carry both UTC and the studio's local time, so "10am for me, 1pm for my student" survives DST. Stripe webhooks generate per-booking invoices with idempotency keys on every write.

The bot lives between Twilio and the ClubReady API. Inbound SMS hit a Next.js route, a state machine resolves intent (book, reschedule, ask), and the API call is wrapped with idempotency so retries never double-book.

Conversation memory and gym configuration live in PocketBase. Each studio gets its own tone, hours, and pricing, and operator overrides are tracked so "the bot said the wrong thing" turns into a fix in minutes.

The pipeline imports BYU's word-aligned TSVs, reconciles edition references against the modern 1879+ chapter/verse scheme, and writes 16,566 verse-level deltas with categorical labels.

The analytics surface is a small set of typed React components reading from Postgres views — stacked bars, treemaps, and a KJV vocabulary comparison — all linkable down to the underlying verse pair.

The desktop build does the real work with custom JPEG and PNG parsers in Rust, a virtualized hex view, and decoded canvas overlays for block grids, scanlines, channels, and bitplanes.

The repair pipeline grafts headers from a known-good donor onto a broken entropy stream and tries common Huffman-table swaps until something decodes.

The catalog and the checkout were the two hard parts. Films, outlines, and sheet music share a single content model so a new title gets indexed everywhere — search, store, and the member dashboard — without copy-paste.

Stripe powers tiered memberships and one-off purchases; webhooks rebuild the entitlements table so "I just paid, why can't I download?" never happens. Auth and download URLs are signed and expiring.

Inventory is one-of-one by default, so the catalog is item-keyed instead of SKU-keyed. When a piece sells, it disappears from the front counter and reappears in the "already shipped" archive.

Checkout sets parcel, crate, or oversized shipping based on the cart's pieces; Stripe webhooks fan out to Resend for the order confirmation and to a packing list the studio prints before it cures the next pour.

The UI sends position fen ... and go depth ... over postMessage; the worker streams info lines back as Stockfish thinks.

Because the engine is local, the product works offline. The PWA shell caches the wasm binary on first visit, so the second open is instant on a plane.

The hard part is making Unity-era content addressable without Unity. Every asset gets a canonical URI keyed by source bundle and path, and cross-references become JSON pointers.

The browser build validates terrain heightfields, cubemap sky, skinned characters, and vehicle physics end to end as the port grows past the original viewer.

Loading 2.5M points the obvious way kills your frame budget. The trick is packing positions into one Float32Array, colors into a Uint8Array, and feeding both to one draw call.

Catalog data lives on Codeberg with Git LFS. A prepare script resolves pointers, downloads gzipped parts, and writes a compact binary the client can stream.

The original is hand-modeled in Blender and rendered with a small Three.js scene; the embed above is the live gh-pages build, frame for frame.

It is the closest thing here to a personal artifact: a small navigable space whose objects are themselves the navigation, instead of a list of links.