|
Hey Reader, This week, we're taking a closer look at some common errors in the .NET and Entity Framework areas, and let me tell you, these mistakes aren't exclusive to beginners! 🎯 .NET OopsiesIn this video, we're going to talk about a few errors that can easily slip through the cracks when you're working with Blazor or creating a .NET Web API. It's easy to overlook these, but being aware can save you a ton of time and headaches. 🛠️ EF Core Code-First MigrationAre you navigating the waters of Code-First Migration with Entity Framework? Then, you'll definitely want to check out this video. It might make your development process smoother and more efficient. If you have questions, feel free to reply to this email. I'm here for more tutorials and to answer any questions. Thanks so much to our community and my Patrons for your support. You are the foundation of this newsletter and my channel. Stay safe, have fun coding, and remember - the best part is creating something new! 💻 Take care, Patrick |
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
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...