My colleague called it "just a batch file"


Hey Reader,

At lunch the other day, a colleague looked at my Copilot setup and said: "It's basically just a batch file, right? You write a script once and run it on demand."

And I had to stop and think. Because that's actually a pretty good analogy. But it's also missing something crucial.

A batch file doesn't read your codebase before it runs. It doesn't know your handlers use a custom base class. It doesn't know you're on minimal APIs. AI Skills do.

video preview

In 13 minutes, you'll see a full vertical slice using MediatR, FluentValidation, and the result pattern. All generated from a single command. Same structure, every time, no re-explaining your architecture, no bloated instruction files consuming tokens you don't need to spend.

This is the difference between automation and intelligence. And once you see it, you can't unsee it.

Take care,

Patrick

P.S. The next Office Hours are coming up soon. This is where we go deeper on exactly this kind of stuff, live, together. If you're not a member yet, now's a good time to join. 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, A developer I know built his whole career on one bet: that young developers would never want to touch old code. So the legacy systems quietly running real companies would always need someone, and he would be that someone. For twenty years it paid. Then AI arrived and went straight for the part he thought was safe. Because the hardest part of modernizing an old system was never the typing. It was the understanding. Reconstructing thirty projects and three contractors' worth of...

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...