﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Bipin Joshi .NET | Thus said a Byte • Insights on .NET and Web Development</title><link>https://www.binaryintellect.net</link><description>Bipin Joshi .NET | Thus said a Byte • Insights on .NET and Web Development</description><copyright>Copyright &amp;copy; binaryintellect.net. All rights reserved.</copyright><generator>RSS Generator</generator><item><title>Real-Time at Last: SSE and SignalR in ASP.NET Core</title><link>https://www.binaryintellect.net/articles/d0294aea-cdb8-4bd7-a6b0-b34c5129035f.aspx</link><description>In Part 1, we walked through the pre-real-time era of server status updates: full page refresh, XMLHttpRequest, Ajax and fetch(), and short/long polling. What all of that machinery was really reaching for is a way for the server to simply tell the client when something happens, the moment it happens. That's what this post covers: Server-Sent Events (SSE) and SignalR, the two mainstream ways to get genuine server push in ASP.NET Core.</description><pubDate>23 Sep 2026 12:00:00 GMT</pubDate></item><item><title>From Page Refresh to fetch(): The Pre-Real-Time Era of Status Updates in ASP.NET Core</title><link>https://www.binaryintellect.net/articles/9091cb0d-0da5-494a-a12c-0decb3bdb53b.aspx</link><description>Almost every non-trivial web application eventually needs to answer a simple question: something is processing on the server, and the user needs to know when it's finished (or how far along it is). Generating a large report. Processing an uploaded video. Running a batch import. Training a model. Provisioning a resource. These operations may take longer than you want a single HTTP request to remain open, so the browser can't just wait around for a response — the user needs a way to check back in.</description><pubDate>16 Sep 2026 12:00:00 GMT</pubDate></item><item><title>One Language to Rule Them? LINQ, Abstraction, and What's Next</title><link>https://www.binaryintellect.net/articles/da6a82a6-b741-4465-b020-0cf2ab5bfedd.aspx</link><description>In Part 1, we traced how .NET's data formats each grew their own query language, and how LINQ emerged as Microsoft's attempt to paper over the fragmentation. In Part 2, we walked through that fragmentation format by format — and kept bumping into the same fact: sooner or later, almost everything gets funneled into objects, and queried with LINQ.</description><pubDate>19 Aug 2026 12:00:00 GMT</pubDate></item><item><title>A Field Guide to .NET Data Formats</title><link>https://www.binaryintellect.net/articles/96302ce2-adbb-491e-8023-02a954cad1ef.aspx</link><description>In Part 1, we made the case that every data format grows its own language because the shape of the data dictates what kind of navigation makes sense. This part is the reference you actually bookmark: a walk through the formats a .NET developer runs into, the native language each one speaks, and a small idiomatic snippet for each so you can see the shape of the code, not just the theory.</description><pubDate>12 Aug 2026 12:00:00 GMT</pubDate></item><item><title>The Many Languages of Data: How .NET Learned to Speak in Formats</title><link>https://www.binaryintellect.net/articles/8b70c7e8-6f7f-4491-a86a-0873dae620be.aspx</link><description>It's a Tuesday afternoon and you're debugging a feature that touches four different pieces of data. First, you write a SQL query to pull a customer record from the database. Then you filter an in-memory list of orders using LINQ. Then you parse a JSON payload from a third-party API, reaching for dot-notation and the occasional JSONPath expression. Finally, you open a legacy XML configuration file and, out of muscle memory, write an XPath query to find the node you need.</description><pubDate>05 Aug 2026 12:00:00 GMT</pubDate></item><item><title>Refactoring as an Act of Care</title><link>https://www.binaryintellect.net/articles/207fae56-6cb9-4a42-a300-d312d1dc25b7.aspx</link><description>Refactoring is usually described as improving code without changing its behavior. That's technically accurate, but it misses something important. Refactoring is ultimately an act of care — for the teammate who inherits your code, for the on-call engineer debugging it at 2 a.m., and for your own future self, who will have forgotten every clever shortcut you took today.</description><pubDate>22 Jul 2026 12:00:00 GMT</pubDate></item><item><title>Backward Compatibility as an Act of Compassion</title><link>https://www.binaryintellect.net/articles/be359529-cc3e-4dbb-91aa-460f97d0b8bd.aspx</link><description>Somewhere right now, a developer is opening a .csproj file that targets net48. Not because they love it. Because the app inside it quietly runs a hospital's billing system, or a manufacturing plant's inventory, or a client's business that has survived three recessions on this exact codebase. Nobody on that team is asking, "Should we rewrite this in .NET 9?" They're asking, "Will this still compile next year?" And the answer, almost certainly, is yes.</description><pubDate>15 Jul 2026 12:00:00 GMT</pubDate></item><item><title>The Fasting Developer: Memory Discipline and GC Awareness in .NET</title><link>https://www.binaryintellect.net/articles/f3c06695-d347-4ede-89a8-6ff39c3e4049.aspx</link><description>There is a quiet assumption baked into most .NET codebases: the Garbage Collector will always clean up. And technically, it will. But the cost of that cleanup — paid in latency, in CPU time, in unpredictable pauses — is what most developers never stop to measure.</description><pubDate>08 Jul 2026 12:00:00 GMT</pubDate></item><item><title>You Are Learning. But Are You Enjoying It?</title><link>https://www.binaryintellect.net/articles/a22d168b-7d32-45fd-829d-933e51884f74.aspx</link><description>There is a question that rarely gets asked in software development, buried beneath tutorials, roadmaps, certifications, and course recommendations: Are you actually enjoying what you're learning? Not Are you keeping up? Not Are you learning the latest framework? Not Have you completed another course?</description><pubDate>01 Jul 2026 12:00:00 GMT</pubDate></item><item><title>The Quiet Codebase: What Vedanta and Yoga Taught Us About Software</title><link>https://www.binaryintellect.net/articles/c7c00c57-12f2-4742-b4fa-40806a931f3b.aspx</link><description>This is Part 2 of a two-part article. In Part 1, we traced the parallel between the growing complexity of modern human life and the growing complexity of modern software — and asked why both seem so difficult to simplify, even when we genuinely want to. Here, we look for answers in an unlikely place.</description><pubDate>24 Jun 2026 12:00:00 GMT</pubDate></item></channel></rss>