I wanted to change my hosting setup for SEO reasons — moving from a client-side SPA to a server-side Blazor application, including admin pages for maintaining the different sections.

Then I got overwhelmed and thought: "Why not play with AI, and get it to do the heavy lifting?" That was the start of a very educational few weeks.

So, mostly whilst watching TV in the evenings, I changed the tech stack, built a deploy pipeline, fought with custom domains, and tried to let AI handle the look and feel. That last one twice. Because apparently, I needed to learn that lesson the hard way.

Along the way I found some tools and approaches that genuinely helped me keep the agents focused and on track. And I found the point where you stop prompting and just write the code yourself.

This isn't a hype talk, and it isn't a cautionary tale. It's an honest walkthrough of what actually happened, what I'd do differently, and what it left me thinking about where all of this is heading.

Oh, and I'll show you the site. 😊

This talk follows a full rebuild of a Blazor WASM / .NET Functions site to a server-side Blazor application running on Azure Container Apps, including a deploy pipeline built from scratch. It starts with the failures — trying to do everything at once and ending up with a mess — through to learning how to tackle the project piece by piece. Along the way: GitHub Copilot agents, Claude Code, and tools like OpenSpec and Squad to keep everything focused and on track.