Why I built this site

For five years I've shipped frontend at Microsoft Teams without a personal site to point to. The work is real but private — internal repos, internal wikis, internal Connect docs. This is the public version.

The constraints I gave myself:

1. The site is the demo. I'm the Performance & Accessibility Champion on my team. If this site is slow or unkeyboardable, I'm not credible. Lighthouse 98+ and zero axe-core violations are enforced in CI; /metrics makes the scores public.
2. Terminal aesthetic. I'm a builder, not a marketer. The site should look like that. The one exception is /resume, which deliberately reads as a formal document — that's the surface a recruiter wants to print.
3. Single page + a few routes. Five anchored sections, three side routes (/resume, /log, /metrics). Keyboard shortcuts (g w, g a, ?) because the aesthetic earns them.

If you're here from a recruiter intro: the resume PDF is at the top right. If you're a peer: /log is where I'll write up what I'm learning building agents.