Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
How I keep Copilot from messing up my .NET code
|
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. Enjoy the breakdown and let me know what you think in the comments. 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 course .NET Web Development with AI and Copilot. Click here to join. And use the coupon code NEWSLETTER for a sweet discount! |
.NET Web Academy
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...