What changed, and why
The original buried the two things a buyer needs first — what it costs and how you get in. The rebuild puts From $100,000, the studio locations, and by appointment only in the first screen. That is qualification, not decoration.
One action, not six
A template offers Home, About, Builds, Shop, Blog, Contact and a cart with equal weight. The rebuild offers one primary action — Commission a build — and a secondary path to browse.
02 — Project
Personal manager
One system for everything that competes for my week: mail, calendar and coursework, pulled through their APIs into a single dataset — then treated as a scheduling problem rather than a to-do list.
Google OAuth & calendar Live
OAuth across two separate provider projects, scoped tokens with calendar write access, refresh handling, and credentials kept in an environment file that never reaches source control.
Calendar mirror & backups Live
Calendars and contacts mirror nightly to local storage over CalDAV and CardDAV, and the whole cockpit backs up to an off-box encrypted repository on a nightly schedule. Both run on cron.
Mail access Live
IMAP engine configured against a 40,000-message account — the raw material for the queue analysis below.
Inbox triage In progress
Little's Law says backlog is arrival rate times time-in-system — so there are exactly two levers. Early measurement says reducing arrivals matters more than handling faster. I had assumed the opposite.
Canvas coursework In progress
Read-only Canvas access to pull assignments and due dates into the same dataset as the calendar, so deadlines and commitments are scheduled against each other rather than separately.
Schedule optimiser In progress
The interesting one. Study blocks and workouts sequenced against finite time — and against the gym's own busy hours, so training lands when the equipment is actually free. Capacity that varies by hour is exactly the constraint a production line has.
03 — Infrastructure
Helping run a real fleet
I work as a co-helper on ThreadSync's infrastructure — a private fleet of Linux virtual machines running real services. It is the part of my experience that no coursework provides: systems that other people depend on, where a mistake has consequences.
Virtual machines
The fleet runs on hypervisors with per-workload VMs — my own among them. I help operate and extend them: provisioning, containerised services behind a reverse proxy, TLS, private networking, and the unglamorous work of keeping things reachable.
The ark file server
A ZFS-backed file server with snapshots and off-site replication. Working around it taught me that storage is a discipline, not a disk — quotas, snapshot retention, and knowing that a backup you have never restored is not a backup.
Reviewed by a second AI
Significant changes get sent to a separate model — Codex — for an adversarial review before they ship. Watching a reviewer find the thing you missed, repeatedly, changes how you write in the first place. This site went through three rounds of it.
None of this is my company or my architecture. I help build and run it, and I have learned more from being in the room than from anything I have been taught.