What I'm building

Open source

Published, documented, meant for other people to actually use.

Experiments

Smaller, rougher, built mostly for myself. No writeups — just what they are and why they exist.

• lastleafChrome extension

  Quietly captures the tabs you close, grouping them by topic into an interactive graph — so the one you actually needed is easy to find again.

• tracewoodlog analysis

  Turns cryptic server logs into plain-English incident reports — finds the actual root cause, reconstructs a readable timeline, and tells you what to do next.

• grovepinChrome extension

  Timestamped notes on video — pin a note to a moment, jump straight back to it later.

Decisions

• Why hueglint's core is framework-agnostic

  React wasn't going to be the only place this needed to run, so the palette logic, validation, and CVD-safety guarantees live in a plain TypeScript core — React just passes a palette name through as a prop. A Vue or Svelte binding later means writing a thin wrapper, not re-deriving the color math.

  Full breakdown →

• Why ladderline has no database

  Promotion evidence needed to be something I could read, diff, and version — not query. Plain markdown files do that for free. The one place it costs something is search across a lot of history, which a database would make trivial and files make you grep for.

  Full writeup →

• Why I didn't over-engineer these projects early

  Every one of these started as the smallest version that solved my own problem — hueglint began as one hardcoded palette, ladderline as a single markdown file I appended to by hand. The architecture (core/binding split, no database, whatever) came after the idea proved worth keeping, not before.