Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
The hidden downside of working as a solo developer
|
Hey friend, Working from home as a .NET developer sounds great. Freedom. No meetings. Full control. But after a while, it gets heavy. You make every decision alone. Architecture. Azure. Refactoring. Deployment. And sometimes you just want someone to say, “Yeah, that’s fine. Ship it.” AI helps. Tutorials help. But real conversations with other developers hit different. In today's video, I talk about why working alone can slow us down and why feedback from other devs matters more than we think. If you build .NET projects mostly on your own, I think you’ll relate. Watch it here 👇 Take care, Patrick P.S. We now have live office hours inside the .NET Web Academy. Join here. |
Patrick God
Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.
Hey Reader, At lunch the other day, a colleague looked at my Copilot setup and said: "It's basically just a batch file, right? You write a script once and run it on demand." And I had to stop and think. Because that's actually a pretty good analogy. But it's also missing something crucial. A batch file doesn't read your codebase before it runs. It doesn't know your handlers use a custom base class. It doesn't know you're on minimal APIs. AI Skills do. In 13 minutes, you'll see a full vertical...
Hey friend, I realized something recently: AI was slowing me down. I’d send a prompt… and wait. Even though I already knew what to do next. So I changed one thing. I stopped using AI like a tool and started using it like a team. Multiple chats. Multiple tasks. All running at once. Watch it below 👇 Happy prompting! Take care,Patrick P.S. If you want help setting this up for your workflow or your team, click here.
Hey friend, Blazor Server or WebAssembly? Lately, I had a call with a student migrating a desktop app… and this question came up immediately. So I made a quick video to break it down: You'll learn: When Blazor Server is the simplest choice When you actually need WebAssembly And when an API becomes necessary Enjoy! Take care,Patrick P.S. Our next live office hours inside the .NET Web Academy start tomorrow. Join here.