The Platform Team as an Economic Function
A platform team is not a cost centre. It changes the marginal cost of safe change, and that is an economic argument, not a tooling one.
Topic
AI systems, engineering judgment, and the organisational choices behind useful automation.
A platform team is not a cost centre. It changes the marginal cost of safe change, and that is an economic argument, not a tooling one.
"Human oversight" is doing a lot of work in AI architecture diagrams. Too much, I think. It usually shows up as a reassuring little box near
Event contracts used to be guidance. With agents on the other end, they're the thing the system actually runs on.
The real architectural decision isn't how fast you process data. It's what you choose to treat as a fact, and whether the machines around it can reason about those facts without asking permission.
Why it is no longer just infrastructure For a long time, the data platform was treated as a supporting layer. A place where data was collected, transformed, stored,
A few years ago, most engineering organizations were constrained by the same thing: writing code was expensive. Not just in budget terms. Expensive in attention. In coordination. In
There’s a particular kind of frustration engineers know well: you pick up a Jira ticket and the description reads something like “Fix the thing from the meeting.” No context. No requirements/details.
How GitHub Agentic Workflows + MCP turned my pull request reviews from context-switching nightmares into fully-loaded briefings