I am a customer-facing cloud and AI advisor. I spend my days helping enterprises translate complex strategy into architecture that actually ships. After years of doing that work, I noticed a recurring problem: the things worth knowing rarely make it into the official documentation. The vendor narrative moves fast. The hype is loud. The durable ideas get buried.
This blog is my attempt to separate signal from the noise.
Why this exists
I have kept mental notes for years. Decisions made, patterns observed, tradeoffs debated in architecture reviews that nobody ever wrote down. Architecture Decision Records exist for exactly this reason. You write them not because you think you will forget, but because you will forget. The “why” behind a decision fades. The context disappears. Technology moves on and the original reasoning goes with it.
This blog is my ADR for the things that matter to me at a given time. Not a product launch. Not a tutorial series. A record of thinking.
What I write about
My day job is cloud computing: Azure, enterprise architecture, resilience, and operating models. But what I think about beyond the job is the history of computing and how poorly we understand it. How the same mistakes keep repeating. How AI is accelerating change in ways that feel unprecedented but echo patterns we have seen before.
You can expect posts on:
- Cloud architecture and the enterprise patterns that actually hold up
- AI readiness, governance, and the gap between what is promised and what ships
- FinOps and reliability, the operational realities that vendor content tends to skip
- The history and trajectory of computing, and why it matters for decisions made today
What this is not
This is not a neutral publication. I have opinions and I will state them. It is not a daily blog. Posts come when I have something worth saying. It is not a tutorial factory. Some posts will be short. Some will go deep.
Who I am writing for
Primarily myself. Writing forces clarity. If you find it useful, I am glad. If you disagree with something, even better.
Signal Over Hype starts here.