Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
GitHub Copilot works but your architecture pays the price
|
Hey friend, I just released a new video and wanted to share it with you. I used GitHub Copilot to build a small Blazor weather app. It worked almost instantly and even used real API calls. At first glance, everything looked great. Then I opened the Razor file. All the logic was sitting in one place. UI, API calls, and business logic mixed together. It worked, but it was not something I would ship. In the video, I show how I fix this using a single refactoring prompt. I move the logic out of the Razor component and restructure the app using Vertical Slice Architecture with feature folders, CQRS, and Mediator. The behavior stays the same, but the code becomes clean and maintainable. If you want to see how to use Copilot for real Blazor apps without losing control of your architecture, this one is worth watching. Take care, Patrick P.S. If you want to learn how to use AI as a real coding partner and not just a code generator, check out my new course .NET Web Development with AI and Copilot. Click here to join, and use the code NEWSLETTER for a discount. |
Patrick God
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
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...
Hey friend, I realized something recently: AI was slowing me down. I’d send a prompt… and wait. Even though I already knew what to do next. So I changed one thing. I stopped using AI like a tool and started using it like a team. Multiple chats. Multiple tasks. All running at once. Watch it below 👇 Happy prompting! Take care,Patrick P.S. If you want help setting this up for your workflow or your team, click here.
Hey friend, Blazor Server or WebAssembly? Lately, I had a call with a student migrating a desktop app… and this question came up immediately. So I made a quick video to break it down: You'll learn: When Blazor Server is the simplest choice When you actually need WebAssembly And when an API becomes necessary Enjoy! Take care,Patrick P.S. Our next live office hours inside the .NET Web Academy start tomorrow. Join here.