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, 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...