Showing archive results for May 2026

Development workflows span terminals, IDEs, background agents, and custom assistants. What matters is whether they draw from the same current source. Learn MCP Server gives any MCP-compatible agent direct access to current Microsoft documentation - one endpoint, nothing to install, no authentication required. What does that look like in practice...

You ship an SDK, a CLI, an API, and developers use it. Now AI coding agents use it too, except they use it differently than humans do. Most of the time you have no idea what's actually happening between "developer types a prompt" and "agent generates code with your technology." Is the agent reading your docs? Is it calling your MCP server? Is it ig...

AI coding agents use your SDK, API, or CLI, but often get it wrong. The stack has layers you can't change and one you can: agent extensions. Learn how to measure whether yours are helping or hurting.

"A bad system will beat a good person [or agent] every time" ~Dr. William Edwards Deming (with apologies) I started vibe coding by writing prompts (often dictated into my phone), refining them with an agent in M365 Copilot, and creating handoff files to use with GitHub Copilot CLI. The results were predictably non-deterministic. Prompt-driven d...

A team was running at 100% RU utilization. Throttles were compounding into retries. P99 latency was degrading. The assumption was obvious: provision more throughput. They didn’t. Instead, they found a single logical partition absorbing more than 80% of traffic. After fixing the data model—without scaling the database—RU utilization dropped to...