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
Where software stops waiting for instructions and starts doing the work.
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.
AI will make some teams smaller. It will not make the work lighter.
The next phase of AI-assisted engineering will not be more magical. It will be more explicit.
Agentic engineering is not the art of asking AI to do more. It is the discipline of making work explicit enough that machines can safely help with it.
The value of a platform is not the tooling. It is the organisational friction it makes unnecessary. Platform engineering is easy to justify badly. A team builds an
"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
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.
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