Why Does AI Need So Many Data Centres?
One agent task can mean 20 model calls. Multiply that by everyone.
Read on Substack →Practical writing for .NET and Azure teams working out where AI fits, from Learn to Build AI.
To learn to build AI as a .NET developer, build one small agent in C# that calls one tool, then add MCP for tools and A2A for agent-to-agent calls. These articles are grouped by theme, each with working code.
Last updated
One agent task can mean 20 model calls. Multiply that by everyone.
Read on Substack →Agents, MCP, A2A and Foundry in C#, with working code, and how to add AI to the systems you already have.
One NuGet package and a few attributes turn your existing Azure Functions into tools any MCP client can call.
Read on Substack →Foundry's workflow builder chains agents without orchestration code, and the docs only show Python, so here is the C# call.
Read on Substack →One agent with its capabilities in composable, versioned markdown files instead of one giant prompt or five agents.
Read on Substack →An orchestrator and a code review specialist wired together with capability-driven discovery.
Read on Substack →MCP is how an agent uses a tool, A2A is how it talks to another agent, and how to design for both.
Read on Substack →A multi-agent C# code reviewer with RAG, MCP filesystem access and clean architecture on .NET 8.
Read on Substack →When the brief is "add AI by end of week", you can start small inside the app you already have.
Read on Substack →A small, live app built around one prompt, and what that taught me about shipping AI features.
Read on Substack →How to get real work done with AI tools and agents, and what is going on under the hood.
Most people stop at a chat tab, and each of the next two levels changes what you can get done.
Read on Substack →Six months of using workspaces with MCP tools and commands as a knowledge worker's second brain.
Read on Substack →A walkthrough of the reasoning loop behind skills, so you can predict what your agent will do.
Read on Substack →What AI means for your career as a developer, and how to learn it without burning out.
AI isn't replacing developers, it's exposing how much software the world still needs and how few of us there ever were.
Read on Substack →Seniors learned on the work AI absorbed first, so where does the next generation come from?
Read on Substack →The few moments in my career when I knew the job was about to change, and why this is one of them.
Read on Substack →Bringing AI into a team, what works, what to expect, and the mess that follows a mandate with no plan.
"Uses AI" is now a job-spec filter and a top-down order, and the gap between the mandate and the day-to-day is where things go wrong.
Read on Substack →Free, no spam, and you can leave whenever you like.