Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
"In the hands of a rookie, AI is just dangerous." He was right.
|
Hey friend, No agenda. No slides. Just real developers talking honestly about what is actually working with AI tools right now - and what is not. One of the first things Paul said set the tone for the whole session: "In the hands of an experienced developer, any AI tool is an accelerator. In the hands of a rookie, it's just dangerous." I keep thinking about that line. Because I think it is exactly right - but it also misses something important. The danger is not AI. The danger is always the same: not understanding what you are shipping. A junior developer who copies AI output, pastes it in, and ships it without understanding what is in there has the same problem as one who copies from Stack Overflow. The AI did not create that risk. The lack of understanding did. What AI does is amplify whatever you bring to it. In this video, I share what came out of that session - the workflows that are actually working, the failure modes nobody talks about, and the specific thing the developers who are thriving right now are all doing differently. It is more honest than most AI content you will find. Because the people in that room were skeptical, practical, and dealing with real constraints. Not a demo environment. Take care, Patrick P.S. These are exactly the kinds of conversations we have in the .NET Web Academy Live Sessions. Real developers, real problems, no agenda. Next session is today! And tomorrow, Wednesday, May 20th, I am running a live Blazor AI Workshop where we build and deploy a real app in two hours. Both are included in the All Access Pass. Join here. |
.NET Web Academy
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
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...
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...