Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
I stopped writing code by hand (and why that is good news)
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 the render mode? A database problem? I had hypotheses. I could weigh the options. And when the answer came back, I could tell whether it actually made sense. Now picture that same moment in a stack you do not know at all. You would have to ask the AI what is wrong and just trust whatever it hands back. No way to know if it is right, half right, or confidently wrong. That is the whole thing. My .NET knowledge did not become worthless when I stopped typing the code. It became the thing that lets me steer the AI and check its work instead of blindly trusting it. I am the pilot. Someone without that foundation is a passenger, just hoping the autopilot knows what it is doing. AI made the typing cheap. It did not make the judgment cheap. If anything, it made judgment the whole game. So these days I would rather deeply understand vertical slice architecture, or how to profile a slow query, than memorize one more API. One of those makes me dangerous with AI. The other, the AI already handles. The full story is in this week's video: Take care, P.S. This pilot-not-passenger thing is exactly what we drill inside the Blazor AI Accelerator. Four live weeks with me, building real things with AI on a foundation you actually understand. Grab an early-bird seat before July 1. |
.NET Web Academy
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, Lately I told an AI I’d see it in 7 hours, and went to bed. It was done in 2. Across two different projects. There’s this thing people call the night shift. You give an AI agent a pile of work, start it in a loop, and go to sleep while it keeps working on your real codebase. I tried it a month ago and could not make it work, the model just fell apart. But with the newest models, it works now. And the surprising part wasn’t that it ran all night. It’s that it ran out of work before...