Stop letting GitHub Copilot decide your Blazor code


Hey friend,

Quick one today.

GitHub Copilot makes form validation feel easy.

But if you are not careful, it slowly decides where your logic lives.

Your app still works.

But the structure gets worse.

In today's video, I show you:

  • A simple Blazor register form
  • How Copilot refactors it the wrong way
  • How to move validation out cleanly
  • How to guide Copilot with clear rules

​Watch the video here πŸ‘‡

video preview​

Have a great start to the new year! πŸŽ†

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.

Read more from Patrick God
video preview

Hey friend, I just released a new video and wanted to share it with you. Watch the video here πŸ‘‡ 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...

Hey friend, I just released a new video and I think you will enjoy this one. In the video, I ask GitHub Copilot to build a real mortgage app in Blazor. The app works. But the code is messy. All the business logic ends up in the UI. Fast results. Bad structure. Then I clean it up properly. Same behavior. Same output. Much better code using services, interfaces, and dependency injection. It shows why Copilot is powerful, but dangerous without rules. Watch the video here πŸ‘‡ Enjoy the breakdown...

video preview

Hey friend, I just released a new video and I think you’ll enjoy it. In the video, I ask GitHub Copilot to build a .NET Web API using a short, vague prompt. The result works, but the structure feels random and messy. Then I run the same idea again with a stronger prompt that forces a clean structure. Feature folders. Vertical slice. Mediator. Fluent Validation. The difference is night and day. Watch the video here πŸ‘‡ Enjoy the breakdown and let me know what you think. Take care, Patrick P.S....