Background & Approach
From Data to Full-Stack.
I didn't come to .NET from a bootcamp. I came to it after years of fighting bad data in regulated infrastructure environments, which is why the applications I build don't ship on top of fragile pipelines.
01 · Foundation
Data Engineering
Years inside regulated infrastructure delivery, Power BI, T-SQL and Azure data architecture for leadership reporting. Bad data is an engineering failure upstream, not a reporting problem downstream.
02 · Discipline
Software Engineering
ASP.NET Core, Blazor and Entity Framework Core. Clean Architecture and SOLID as defaults, not aspirations, APIs designed to be testable, debuggable, and quietly handed over.
03 · Delivery
Cloud on Azure
End-to-end Azure deployment with CI/CD pipelines, security patterns and structured monitoring. Applications that ship into production and stay there, without weekend pages.
04 · Practice
Independent B2B Consulting
Remote-first engagements across EU and UK markets. Direct contracts, end-to-end ownership, no agency overhead, Power BI analytics and .NET applications delivered by the same engineer.
Why this matters for you
Most .NET developers can't read a fact table. Most Power BI specialists can't ship a Clean Architecture API. I sit at that intersection on purpose.
You get one engineer accountable for the whole vertical, the SQL layer, the .NET application sitting on top, the Azure environment it runs in, and the Power BI surface leadership actually reads. No handoffs, no integration gaps, no finger-pointing between specialists.