THE WORK SAMPLE
How this site is built
You’re looking at the work sample. This page is how it’s made — and how I made sure every word on it was true before it went up.
The build
It’s a plain static site — hand-written HTML and CSS, no framework, no build step, and no JavaScript at all. The menu you’re using works with JavaScript switched off; it’s a pure-CSS toggle. One shared stylesheet drives every page, so adding a new page is copy one file and add one link — nothing else to wire up.
Everything loads from this one address. No CDNs, no Google Fonts, no analytics, no trackers, no cookies, no third-party anything. The type is either your own system fonts or font files I host myself — never fetched from someone else’s server. The icons are drawn inline. The page is keyboard-navigable and respects “reduce motion” if you’ve set it. Don’t take my word for any of it — hit “view source.” What you see is what there is.
The result
I self-host this on hardware I control. It scores an SSL Labs A+, behind locked-down security headers and a strict content policy. Nothing a visitor does on here is sent to anyone but this site — there’s no one in the middle counting your clicks. Fast, private, and boring on purpose. Boring is the goal: nothing fragile, nothing to break, nothing phoning home.
How I ran it
Same way I run everything: the AI did the typing, I did the directing — designed, checked, and signed off by me, built by AI under the checkpoints I run. Then I did the part most people skip.
Before this site went live, I had independent agents fact-check it. I pointed fresh, read-only AI agents at the actual code and repositories behind every project I mention here — one per project — and had them check every claim, every version number, and every count against what’s really on disk. They caught stale numbers, one place I’d oversold myself (a “tested” that didn’t have the tests to back it), and a couple of places I’d undersold myself. I fixed all of it before you ever saw it. That’s the whole point of how I work: nothing here is dressed up, because it was checked.
What I don’t publish
How this is hosted — the box, the network, the setup behind it — I deliberately keep off the public internet. Posting your own infrastructure is how people get themselves hacked, and not posting it is basic operational security. It’s the same judgment I’d bring to your systems. Happy to walk you through the whole architecture in an interview.
That’s the site, and that’s how I work. Let’s talk about the job →