I built a Blazor app in 30 minutes (here's the part that matters)


Hey friend,

This week, I built a working Blazor app from scratch in about 30 minutes. But that's not really the point.

The point is how. Not by throwing a prompt at Claude and hoping for the best. But by thinking about architecture first, defining instructions and skills for the AI upfront, and then letting it implement while you stay in control and review the output.

That's the difference between AI doing your job and AI doing the boring parts of your job.

The video walks through exactly that: vertical slice architecture, AGENTS.md, AI skills, the whole setup. And yes, there were some errors towards the end. We fixed those, too. That's part of it.

Watch the video here

video preview

If you want to take this further and build something that actually gets deployed, I'm running a live two-hour Blazor AI workshop next week. We go from that same starting point all the way to Azure.

Take care,

Patrick

P.S. Members of the .NET Web Academy All Access Pass join the Blazor AI workshop for free. Join here.


.NET Web Academy

Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.

Read more from .NET Web Academy

Hey friend, The other day I found a bug in StackBuddy, an app I built. Normally I'd open it, file a ticket for myself, and move on. Instead I turned to my AI and just said, "log a dev ticket for that." And it did. A real ticket in my own bug tracker. Title, description, priority, the whole thing. I never opened the actual app. The thing that makes that possible is called MCP, Model Context Protocol. Ignore the name for a second. Out of the box, an AI can only talk. It writes and explains, but...

Hey friend, I don't really write code by hand anymore. I describe what I want, and the AI builds it. For a while, that scared me. If I am not writing the code, does everything I spent years learning still matter? Does my stack matter at all? If you are a developer right now, I would bet you have felt some version of that too. Here is where I landed. It flipped the whole thing for me. The other day I was debugging a slow app, talking it through with the AI. Would WebAssembly help here? Is it...

video preview

Hey friend, Lately I told an AI I’d see it in 7 hours, and went to bed. It was done in 2. Across two different projects. There’s this thing people call the night shift. You give an AI agent a pile of work, start it in a loop, and go to sleep while it keeps working on your real codebase. I tried it a month ago and could not make it work, the model just fell apart. But with the newest models, it works now. And the surprising part wasn’t that it ran all night. It’s that it ran out of work before...