I build production software and I stay on call for it.

Nexus is the customer-relationship platform I wrote to handle the sales pipeline, email campaigns, service desk, and knowledge base for the travel business that TravelTamers supports. It contains fifty-four tables, a five-tier role-based access system, and a Socket.io layer that pushes notifications to whoever is looking at a record when someone else modifies it. Nexus lives in its own set of containers on the same VPS as TravelTamers, and the two of them communicate through the fire-and-forget sync I described above.

Groups is a smaller application that handles collaborative trip planning. One person creates a trip, other members propose itinerary legs, the group votes on what stays, and the application generates a cover image for each trip using Replicate's FLUX model. It is written in plain Express with server-rendered EJS templates rather than the React stack I use elsewhere, because I wanted one part of the platform to live in a lower-ceremony framework as a point of comparison for myself.

Miles is the conversational agent that appears on the marketing pages of TravelTamers. By default he is a thin wrapper around Claude: he reads an inquiry, asks Perplexity for any time-sensitive pricing or availability information it needs, and drafts a three-option itinerary with sources attached. When Claude is unreachable, either because of trouble on my end or an outage on Anthropic's, he falls back to a small open-weight model that runs on the VPS itself, so a visitor always gets an answer of some kind.

My n8n instance holds somewhere around sixty workflows that handle the interstitial work the rest of the platform would otherwise have to do itself. The ones that earn their keep every day are a daily social-content pipeline, which ingests trending travel news, filters it through a local model, asks Claude for editorial judgment on the top five stories, and hands the result to Replicate for image generation; a lead-scoring flow that runs whenever a form is submitted; and a recurring passport-expiration check that compares every upcoming booking against every passport on file. Everything else is a small sync or notification that was easier to write as a workflow than as a cron job.

Filename-as-Specification is a methodology I developed for keeping AI coding agents from hallucinating. The core idea is to encode the full specification of a file into the filename itself, in a grammar the agent parses before it writes any of the body, so that the agent cannot drift from what was asked for without first changing the name of the file. An architect agent proposes the names, a code agent implements the bodies, and a validator walks the resulting tree in six phases to confirm that what got written is what the filename demanded.

Refined Vacations is an eco-adventure travel brand for which I built and continue to maintain the marketing site. Before we listed anyone, I audited one hundred and eleven candidate partners and kept the seven whose sustainability claims held up under scrutiny, and the gap between those two numbers is the whole argument of the brand. The site itself is hand-written PHP on top of a Fibonacci-derived CSS system, because the voice of the brand is skeptical of greenwashing and I wanted the visual system to feel considered rather than templated.

Pickleball at Sea is a small business that organizes pickleball tournaments on cruise ships and at resort properties, and the site I wrote for it handles registration, bracket generation, scoring, photo galleries, and the event calendar. It is by far the smallest system on this page, and although my family is impressed with none of the others, they are impressed with this one, which is probably the most accurate review the site will ever receive.