Platform engineering is often described as an organizational response to scale: too many teams, too many services, too many deployment paths, and too much operational friction. That framing makes it s...
PostgreSQLGitHub Actionsci-cd+4
How to coordinate multiple coding agents without turning your repository into a collision zone.
A single coding agent can feel like a very fast pair programmer. A group of agents can feel like a small engineering organization that never sleeps—until they edit the same file, infer different requi...
GitHub Actionsci-cdTypeScript+3
A practical guide to exposing .NET capabilities safely through the Model Context Protocol.
Large language models are capable of reasoning over instructions, but they cannot safely operate your systems just because they can describe them. They need a controlled interface: a contract that def...
.NETcsharpAI/ML+2
How Proxmox VMs, k3s, Traefik, storage, and disciplined operations form my home platform.
A homelab becomes substantially more useful when it stops being a collection of experiments and starts behaving like a platform.
That is the goal of my k3s-on-Proxmox stack. It is not intended to imi...
GitHub Actionstraefikproxmox+3
How deeper runtime involvement could make high-concurrency .NET services more efficient.
Async code has always been one of .NET’s most productive abstractions. A request handler can await a database call, an event consumer can pause for a message, and a background worker can wait on a tim...
.NETcsharprest-apis+1
How the MCP Registry makes agent integrations discoverable, versioned, and safer to adopt.
AI agents are only as useful as the tools they can discover and use reliably. A model may be able to reason about a deployment failure, summarize a customer record, or draft a database migration—but i...