Every pull request previews · every merge ships
Twenty years, seven industries. Different floors, different systems — the same problem: data has to move, it has to land, and it has to be trusted. This is the merged log.
Started on the floor — end-user support, help desk, network operations — and grew into the person who writes the dashboards the operators read every shift.
MERGEDData for a portfolio of client companies: executive KPI dashboards, WMS reporting, and the streaming pipelines that fed production-efficiency boards in real time.
MERGEDA consulting shop that builds data products for companies in staffing, contract manufacturing, 3PL, and distribution. The company is the portfolio.
OPENUntangled a monolithic platform — SSIS, Python, C#, and Spark moving billions of records every few minutes — and rebuilt it so the people using it could trust it.
MERGEDAzure and Power Platform: a system that took raw PDFs, normalized them with machine learning, and turned them into customer reports that no longer required an archaeologist.
MERGEDMedallion architecture on Microsoft Fabric — pipelines, Dataflows, Spark, lakehouse, warehouse — and PowerApps that put a stack of paper forms out of its misery.
MERGEDThe build in flight: a restaurant group's whole data estate moving from Azure to Fabric. Pipelines, lakehouse, warehouse, streaming — in production.
OPENOne kind of work: taking a data estate from where it is to Microsoft Fabric — and leaving it running. Microsoft-certified Fabric Analytics Engineer, with two decades of pipeline work behind it.
The whole estate, moved in an order that keeps the dashboards working on day one: pipelines, lakehouse, warehouse, streaming.
PRODMedallion architecture built to be operated, not just drawn: bronze to gold, with the lineage to prove it.
PRODHigh-volume, low-latency — the kind that has to be right every few minutes, not every few days.
PRODIf the estate needs to move, the first step is a conversation. No forms, no tracking — an email, answered within a day or two.
edward@erco.devThe blog, kept like a changelog: one note per meaningful change — in the work, the lab, or this site itself.
What it means to ship a personal site the way a platform ships: source in the repo, previews per branch, a production node you can reach.
SHIPPEDThings that don't ship to production sit here on purpose. They keep the machine honest about what a person is when the build is idle.
If the game's interface is the plot, I'm in. The progression system is the character arc.
I read it for the systems and stay for the worlds.
The RTX 3090 in the 42U rack exists so the weekends have a use.
The one build of mine that's open to anyone — a club for people building with agents.
club.erco.dev →Every pipeline ends at production, and so does this work: it only counts when it's running somewhere someone depends on. If your estate needs to move — Azure to Fabric, or onto rails that exist — that's the build I take.
The whole page is one email away from the next deploy. I answer within a day or two — email only, no phone, no forms.
edward@erco.dev