T3 Code provides a convenient interface for working with coding agents such as Claude Code and Codex. One of its more interesting features is that the T3 client doesn’t need to run on the same computer as the agent.

That means you can start a Claude Code session on your development workstation, walk away, and continue interacting with that same session from your phone. If you only use Claude Code, you can achieve something similar using Remote Control. Other agents offer or will likely offer similar features as well. The advantage of T3 is that it integrates with many different LLM providers, currently including Codex, Claude, Cursor, Grok, and OpenCode.

If your .NET pods are each using 1–2 GB of RAM, you may be leaving a lot of pod density — and money — on the table. Here are the first things I would look at.

1. Set Realistic Kubernetes Memory Limits

Do not let every pod believe it has access to the whole node.

1
2
3
4
5
6
7

resources:
  requests:
    memory: "512Mi"
    cpu: "100m"
  limits:
    memory: "768Mi"
    cpu: "1000m"

This gives the .NET runtime better boundaries and helps Kubernetes schedule pods more predictably. The .NET GC specifically looks at the container’s memory limit (not the request) to decide how much heap it’s allowed to use, so an unset or overly generous limit is what lets the managed heap grow far larger than you intended.

A developer I was chatting with recently raised a question I’ve been hearing more and more:

Since we can produce code so fast now, does the code actually matter that much? Assuming the code fulfills the requirement through actual user testing, who cares what the code looks like? We’re just sitting at another layer of abstraction. Once we got 2nd and 3rd generation languages, did you care what assembly they output - as long as it did what you wanted?

Claude Code’s agent teams feature lets you spin up multiple Claude instances that work in parallel, each in its own visible terminal pane. On Windows, visualizing this properly requires WSL2 and tmux — here’s how to set it up from scratch.

Prerequisites

• Windows 10/11 with WSL2 available
• A Claude Code subscription (Pro or Max) with Opus 4.6 access
• Your repos somewhere accessible (e.g. C:\dev\github\reponame)

Step 1 — Enable WSL2 and Install Ubuntu

Open an elevated PowerShell and run:

AI coding agents are only as good as the information you put in front of them. Every byte of context you load into an agent’s context window is space that could have been used for the code, conversation, or task at hand. Getting this balance right requires the same design instinct that makes good UIs, great games, and well-structured APIs: Progressive Disclosure.

What Is Progressive Disclosure?

Progressive Disclosure is the principle of revealing complexity incrementally rather than all at once. Instead of bombarding an audience with everything they might ever need to know, you give them just enough to act now, with clear pathways to more detail as it becomes relevant.

“Software developers fail in two ways: they build the thing wrong, or they build the wrong thing.”

These two separate failure modes are worth exploring independently, because they have different root causes and very different consequences. And Agentic AI “developers” face the same challenges, but can do both much more rapidly than their human counterparts.

The Two Ways Developers Fail

1. Building the Thing Wrong

Building the thing wrong means the technical execution is flawed. The requirements may have been understood correctly, but the implementation was flawed.

One of the foundational promises of cloud computing is elastic, near-infinite scalability. You pay for what you use, and when demand spikes, the cloud scales with you. It was supposed to be the end of capacity planning, the death of “we need to buy more servers” conversations. So why is Anthropic—one of the best-funded AI companies in the world, running on the infrastructure of Amazon and Google—throttling its users during peak hours?

If you want to stand out, you need to have your own identity. This is true whether you’re talking about you, the person, individually, or your business. You can’t really have your own distinct identity if everything about you is just vanilla, off-the-shelf stuff that anyone else could easily do if they chose to do so. I’m mainly focusing on businesses and their branding and positioning here, but you’ll see parallels that apply to personal brands as well.

DotNetConf (.NET Conf) is a long-running virtual conference hosted each November with the release of a new version of .NET. Its sessions are published to YouTube each year. What have been the top sessions each year? I wrote a tool to pull the stats year by year (since 2021) to see.

Also, why do I keep giving (updated) versions of the same session, Clean Architecture, each year (like last November as covered by Jeremy Sinclair)? There are some who have found it a bit… repetitive (though I do mix it up year to year):

In 2026 we can all agree that AI and agentic development are certainly exciting topics which many see yielding great productivity gains. But as the investor-subsidized pricing of these services gives way to realistic and profitable business models, where will the real costs land?

As many businesses downsize staff or pause hiring to see how these new models and tools actually perform in the real world, the trillion dollar question is: