Projects

Each entry states the problem and why I built it — drawn from the previous site and public references. No invented metrics.

The Boring Tool

Beta product

Problem: Product surfaces often lean on hype and dashboard theatre instead of a deliberately simple face for the boring work that needs doing well.
Why I built it: The Boring Tool is an early product. Its public page is the face of the beta: request access, and an admin reviews the request by hand — there is no public self-registration.

Betty Connect

VS Code extension — Betty Blocks

Problem: Betty Blocks templates lived in the platform. Editing them in VS Code, and writing page-builder custom components there, wasn’t a first-class path.
Why I built it: I built Betty Connect so you connect VS Code to a Betty app, get a template tree in the activity bar, save back to Betty Blocks, plus snippets for custom components.

KMOSC

Personal project — Keyboard Maestro + OSC

Problem: Keyboard Maestro macros are powerful on the Mac, but triggering them from OSC (for live setups, tools, or other machines) was not a solved, shippable path.
Why I built it: I built KMOSC to run Keyboard Maestro macros over OSC, shipped macOS builds and a KM plugin, and published the project on GitHub. A product page used to live at /app/kmosc on this domain.

Public releases for Apple Silicon and Intel, plus a Keyboard Maestro plugin zip
Earlier site copy also mentioned a goal to integrate OBS control by OSC

GitHub Historical page