Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
I never opened my own app. The bug got filed anyway.
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 it can't actually do anything in your real tools. MCP is the connector that changes that, like USB did for devices. A common plug, so any AI can read from a tool, write to it, and take real actions in it. And that quietly flips something. Your tools stop being places you visit and become capabilities your AI can compose. You don't go to the app to do the task anymore. You state the outcome, and the AI reaches into whatever tool can deliver it. In the new video I show it live, filing that bug ticket and then scheduling a Substack note, both from a single sentence. But here's the part I actually want you to take away. When your AI can take real actions in your real systems, the cost of a confident mistake goes up. It filed the ticket perfectly, but it could just as easily file the wrong thing, fast. So the skill that matters isn't the clever prompt. It's being able to look at what the AI did and know if it's right. You're still the pilot. The AI is a fast, literal co-pilot. The trick is keeping your hands on the controls. Take care, P.S. Giving your own apps an MCP so your AI can operate them, on a foundation you actually understand, is exactly what we build together in the Blazor AI Accelerator. Four live weeks, small group, real projects with me. Early-bird seats are open through July 1, so this is pretty much your last call: grab a seat here. |
.NET Web Academy
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
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...
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...
Hey friend, For almost every .NET project I start now, I reach for the same architecture. Not clean architecture. Not the classic controller, service, repository stack that pretty much every tutorial taught us a decade ago, me included... I reach for vertical slice architecture. In my latest video, I break down exactly what it is, why it became my default, and the part almost nobody is talking about. Now that we are all building alongside AI, the rules for choosing an architecture have...