|
Hey friend, Knowing how to prompt is not enough anymore. If you want to land clients or your next role, you need real projects you can show. And one of the best places to start is a portfolio page. So in my latest video I build one from scratch using Claude and VS Code. Blazor, static server-side rendering, a clean single-page design, the whole thing. But here is the part that matters. I let Claude do the heavy lifting - the layout, the sections, the design, even pulling real info from my GitHub and LinkedIn. But I stayed in charge the whole way. I knew what SSR meant, what render modes to use, what architecture made sense, and what to fix when the AI did something I did not want. That is the one rule. Everything on that page should be something you can actually explain. Because if AI builds the whole thing and you have no idea how it works, it will not help you in the interview. In the video, you will see the full build, the prompts I used, how to pull in real data, the Dribbble screenshot trick for restyling the whole page in one prompt, and where the AI gets it wrong, so you know what to watch for. Take care, Patrick P.S. If you want to build a real-world Blazor app with AI and ship it to Azure, that is exactly what the Blazor AI Workshop covers - three hours, empty folder to deployed app. Details here. |
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
Hey friend, Building a Blazor app is the easy part. Getting it deployed so other people can actually use it is where most developers get stuck. It is also one of the biggest reasons developers joined the Blazor AI Workshop last week. The "I can build it, but I cannot ship it" gap is real. So I made a focused YouTube video showing the simplest way to deploy a Blazor app to Azure. Watch on YouTube A tic-tac-toe game with SignalR, real-time updates, a history feature with SQL Server. Deployed to...
Hey friend,A few weeks ago, I was on a live call with a group of .NET developers. 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...
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...