Server-Backed Backends and Peripherals Go Physical
Migrating backends to server APIs with NATS pub/sub, adding microservices, and building the peripheral slot system with the Canada Goose game.
Development journal entries tracking progress on various projects.
Migrating backends to server APIs with NATS pub/sub, adding microservices, and building the peripheral slot system with the Canada Goose game.
Identity got real: guest sessions, passkeys, and a server‑backed auth surface, plus gopher content routing, Z‑Machine version wiring, and a formatting sweep.
Shipping the TI CC-40 backend with authentic CALL commands and audio, plus a full IVR phone tree system.
Floppy, hard drive, and cassette peripherals with Kansas City Standard encoding, plus a peripheral audio bus that makes the machine feel physical.
Kubernetes/K3s deployment configs, CI/CD scaffolding, schema-driven API generation, and the Star Trek BASIC backend.
Moving the web app to a proper structure, migrating parsers to Pest/Pratt, and building the Z-Machine opcode engine.
Pushing the Z-Machine interpreter forward with decoder work, text handling, and SAVE/RESTORE—plus content-addressable storage with S3 sync.
Transforming a dungeon crawler demo into a persistent roguelike with progression, daily challenges, and meta-unlocks—all in one session.
Intel 8088 demos, Zig-based 6502 experiments, and migrating the frontend to TypeScript for better type safety.
Splitting the repository into clear domains—cores, languages, assemblers, BIOS—and making future work less of a guessing game.
Tightening the build pipeline for modem-core WASM, dynamic backend loading, and making the modem behave like a real modem.
Fixing CRT modem and BBS bugs—the quiet foundation work that keeps a larger project from getting weird later.