Why the change?

WordPress served me well, but I wanted something that fits better into my workflow:

• Markdown-first — I write in markdown already for GitHub READMEs, docs, and notes. Now my blog posts use the same format.
• Version controlled — Every change is a git commit. I can review, revert, and collaborate the same way I do with code.
• Fast and simple — No database, no plugins to update, no security patches. Just static files served from GitHub’s CDN.
• AI-friendly — Markdown files are easy to work with programmatically. I can use AI tools to help draft, edit, and publish.

What’s here

The site is organized around what I actually do:

• Projects — The demos and tools I build, with architecture details and links to code
• Talks — Conference presentations with context about the audience and topic
• Videos — My YouTube content, organized and easily browsable
• Blog — This is where demos, tutorials, and lessons learned will live
• Resources — Downloads, slides, lab guides, and reference materials

What’s coming

I’ll be migrating my best content from the old site and publishing new posts regularly. Every demo I build will become a blog post, a video, and a GitHub repo — everything feeding everything else.

Stay tuned.