Most of Your Job Is Peoplefae5fac

The most frustrated person on a team is rarely the least competent one. More often it's someone good at the work who can't understand why everything around the work is so slow. Past basic competence, what separates the effective people from the stuck ones is mostly how they handle the people around the work: giving your boss the information they need, letting your team watch what good looks like, handing other teams a request they can say yes to, and permanently removing the problems that keep requiring you. Manage up, model down, and keep working yourself out of a job.

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 goes straight at that class of failure. The protocol is stateless over Streamable HTTP, discovery is explicit, OAuth discovery is hardened around RFC 9728, and MCP Apps let a tool return a sandboxed interface. MCP is turning into ordinary Internet infrastructure, and the interesting engineering starts after the JSON-RPC leaves your process.

The Discipline of Undoa616220

Ctrl+Z may be the most trusted keystroke in software, but production systems aren't text editors. Every conversation about AI agents eventually turns into a conversation about trust, and the useful kind of trust comes from knowing what happens when the agent gets something wrong. Undo is an operational discipline that runs from design and validation through rollback, compensation, and learning, and the more we let agents act instead of advise, the more that discipline has to exist before we hand them the keys.

Can I Deploy Your Code?14078bb

Talk to Dave. Only Sarah knows that pipeline. Use Jenkins, but not that Jenkins. Never on Fridays. Those are all answers to one of the fastest diagnostics in software: can I deploy your code, right now, safely, using the process the team claims to trust? A clean answer means deployment is a repeatable process. An answer that routes through Dave means you've found a fragile system protected by institutional knowledge, where every deployment that needs a specific human is technical debt the organization has learned to call expertise.

AI Speeds Up Execution, Not the System Around Itee40c71

A developer leaves standup with a ticket and comes back the same day with an implementation, a migration plan, and three pull requests; a year ago that was a week of work. AI made execution dramatically faster, but most teams are held back by planning and validation, and AI does little for either by default. Speed up only the middle of the delivery system and the work backs up at review, testing, and deployment. The fix is to improve the whole loop, starting with the two stages AI left alone.

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. Underneath is a tradeoff between utilization efficiency and economies of scale: serverless makes waste visible as usage, and 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.

Don't Triage at the Customer's Expense4f0391c

Production is broken, engineers are on a call, and every few minutes a voice says "we think we're close." Everyone is busy, nobody is lazy, and the customer is still broken. Once a defect is in production, the customer should not become part of your debugging environment. Triage that feels like progress (more logs, another build) often means the customer keeps absorbing the failure while engineering looks for certainty. Stop the bleeding first, then diagnose.

Work Yourself out of a Job42e5e3e

'I am the only one who knows how to do this' sounds like a flex, but most of the time it means part of the system only works because you are standing next to it. Working yourself out of a job means removing the broken, fragile, one-person-dependent parts of your work so the system no longer needs babysitting. The engineers worth keeping make their hardest problems boring, hand them off, and earn their way into bigger ones.

Boring Software1377668

The demo worked, the team hit the date, and everyone felt good for about thirty minutes. Then the support tickets started. Boring software can be as clever as you like to build. The part that should be boring is running it in production, with practiced rollbacks, clear ownership, and nobody relying on heroics to get through the week.