|
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. 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 |
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
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...
Hey friend, A year ago, I said AI coding tools weren't the future. I want to correct that. The distinction I missed: there's a real difference between vibe coding (copy-paste until it compiles, no understanding required) and skilled AI-assisted development (you own the architecture, AI implements it, you review the output). I was criticizing the first and accidentally dismissing the second. In 2026, skilled AI-assisted development is the professional standard. Not using these tools is now a...
Hey friend, We once spent five days in meetings debating a single delete button. Whiteboard sessions. A compliance guy nobody invited. A product manager who scrolled Slack for what felt like forever. And still no decision. Until Tom walked in on Monday morning, asked one question, and shipped it that afternoon. In this video, I tell the full story and walk you through the four questions that should end this debate on any team, in any codebase. Take care, Patrick P.S. We go deeper on exactly...