The Nuts and Bolts of a Modern MCP Servereb13844

I had a remote MCP server that worked with every client I pointed at it, until Grok's OAuth flow asked a discovery question no other client had asked and the integration stopped before a single tool call. The July 2026 MCP specification is aimed at exactly that class of failure: the protocol is now stateless over Streamable HTTP, discovery is explicit, OAuth discovery is hardened around RFC 9728, tools carry icons and identity, and MCP Apps let a tool return a real sandboxed interface. MCP is turning into ordinary Internet infrastructure, and the interesting engineering starts after the JSON-RPC leaves your process.

The Repository Should Match the Way the Software Ships10fd32f

A five-line change should not take five days to ship, but chase a small fix across four repositories and that is what happens: the code is the fast part, and the coordination burns the week. Arguments about monorepos usually start with tooling, but the real issue is coordination. A repository structure is a delivery model: it encodes ownership, dependencies, release flow, and how much coordination people need before they can safely ship. Size repositories around deployables and publishables so the repo boundary tells the truth about how the software actually ships.

The Real Cost Tradeoff Between Serverless and Hosting2518763

We only pay when it runs, says one team; this instance is cheaper at volume, says the other. Both can be true, and both can lead to bad decisions. The real tradeoff is not serverless versus servers, it is utilization efficiency versus economies of scale. Serverless makes waste visible as usage; hosting hides it as idle capacity. The cheapest system is the one whose cost model matches the shape of the workload and the maturity of the team operating it.

Why Long-Running Branches Are a Tax on Everyone Elsed3c312f

I started writing software before source control was a given: you found out who changed a file by asking around. Git made creating branches cheap, but it never made integrating them cheap. Long-running branches feel productive for the developer who opens them, but the cost lands on everyone else through delayed integration, hidden assumptions, and uncertainty that surfaces right before a release. Trunk-based development is less a trend than the natural consequence of taking CI/CD seriously.