|
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 the night was over. My latest video breaks down exactly what happened, the actual prompt I gave it, the one command that makes the loop run on its own, and the honest look at where this is genuinely useful and where it isn’t. The short version: I asked it to build a performance profiling feature and then actually use it to find and fix slow pages, plus add loading skeletons everywhere. I ran it on two projects at once, mine and a ticketing system I’m building. I woke up to two working apps, all committed in steps I could review. Then I checked the timestamps. The last one was around 2am. It hadn’t run out of steam. It finished everything I gave it and stopped. Which flips the whole question. It’s not “can the AI last all night,” it clearly can. It’s “how much well-defined work can I actually line up for it.” In the video I get into the real reason this works now, why the weekend might be the better move than overnight, and the one thing that made it safe to let an agent run loose across two codebases while I slept, which has nothing to do with the AI and everything to do with how the projects are built. Take care, Patrick P.S. The reason I could trust an agent overnight comes down to clean, AI-ready project structure. That’s exactly what I cover in my free Blazor AI Jumpstart course, the setup and workflow I wish I’d had when I started. |
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
Hey friend, For almost every .NET project I start now, I reach for the same architecture. Not clean architecture. Not the classic controller, service, repository stack that pretty much every tutorial taught us a decade ago, me included... I reach for vertical slice architecture. In my latest video, I break down exactly what it is, why it became my default, and the part almost nobody is talking about. Now that we are all building alongside AI, the rules for choosing an architecture have...
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. Watch on YouTube But here is the part that matters. I let Claude do the heavy lifting - the layout, the sections, the design, even pulling real...
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...