The site is its own pipeline
A personal site is a strange product. It has exactly one customer — the person deciding, in about ninety seconds, whether to send an email. For most of my career I've built things for other people: dashboards, pipelines, warehouses, moving parts. And for most of that same time my own site was a brochure. A page that talked about the work.
This year changed that. The job I've been doing since the spring has been moving a restaurant group's entire data estate from Azure to Microsoft Fabric — pipelines, lakehouse, warehouse, streaming — in an order that keeps the dashboards working on day one. When that kind of work is your daily reality, you start reading everything else the same way. A personal site is a data estate: it has a source, it has a path, it has a destination, and it either lands or it doesn't.
So this site is a pipeline. The graph you saw above it is its actual topology, not a metaphor. It is built from a repository: a folder, a static site generator, a pull request, a merge, a deploy on the free tier of Azure. The token that landed on the production node a few seconds ago is the deploy that put these words in front of you. Every time this site changes, that line runs again. The point isn't the theater of it. It's that a portfolio made by a data engineer shouldn't describe reliability — it should have it.
The second line
There's a second line on that page, and it's dashed, because it has already run. Five nodes, 2006 to 2026. My career went healthcare, then operations, then utilities, waste, distilling, hospitality — seven industries in twenty years. I don't need to say I'm adaptable; the line shows it. Every one of those industries had the same problem: data that has to move, that has to land, and that has to be trusted. The floor you're standing on changes. The problem doesn't.
Two rows are amber
You'll notice that two rows in the merged log are amber, not green. The consulting company is still being built. The migration in flight is still in flight. I could have made the whole page green. I didn't. If a status panel on my own site says everything is fine, I don't know what to believe about anything else it says.
What's on sale
The unglamorous version of all of this: Azure-to-Fabric migrations, lakehouse and warehouse builds, streaming and operational pipelines. If you have an estate that needs to move, the first step is an email — edward@erco.dev — and I answer within a day or two.
Release 0001. Deployed.