Recent Posts

Every AI query burns real electricity, real cooling, and real carbon. Here's why treating carbon footprint as a query optimization problem - not a sustainability afterthought - is an architecture decision, and the patterns and cloud tools that make it measurable.

Software defaults carry culture, and translating the prompt doesn't fix it. Here's why cultural inclusion and user autonomy have to be architectural choices - not features you bolt onto the UI.

Most AI failures aren't prompt engineering problems - they're system design, data pipeline, and architectural failures. Here's why responsible AI has to be built into the stack, not bolted onto the prompt.

For those who haven't kept up on Aspire in 2026, you'll find it has become a whole new beast.

In the sixth post of our SignalR for Blazor series, we bring it all together - the best practices that keep real-time apps reliable, the patterns worth repeating, and the anti-patterns that cause the most pain.

In the fifth and final post of our SignalR for Blazor series, we look at real-time notifications - the notification types, hub design for sending and receiving, and a complete notification center example.

In the fourth post of our SignalR for Blazor series, we look at streaming data updates - continuously pushing data from the server to clients, perfect for dashboards and monitoring applications.

In the third post of our SignalR for Blazor series, we build a real-time collaborative text editor where multiple users can type in the same document and see each other's edits instantly.

In the second post of our SignalR for Blazor series, we take a closer look at connections and hubs - what they are, how clients connect, and how data flows between client and server.

What is real-time communication, what is SignalR, and why does it pair so naturally with Blazor? This is the first post in our SignalR for Blazor series.