I run technology like a P&L and review architecture and code like an engineer.
I make expensive, irreversible technology decisions safe — including the risks that never show up in plain sight or in the numbers. I work at the point where technology decisions become financial commitments, regulatory exposure, and long-term risk — for boards whose technology bill is a major line item and whose platform failures make the news.
I've done this work under real scrutiny: modernizing a major airline's platform under relentless uptime and passenger-experience demands, and a top Philippine bank's under regulatory and financial watch. I read the financials, the contract, and the architecture — and what each implies for operations.
And I don't gamble to find out what works: I plan, pilot, pivot, prove — then production.
Cloud cost savings from optimization isn't a saving — it's a receipt for past neglect. It measures the technical debt you let accumulate and the mess you finally cleaned. And you don't judge a house by how much dirt you swept up last week.
The most effective distortions contain no lies. When someone invents a fact, you can disprove it — but when someone assembles true facts into a false shape, there's nothing to disprove. Every claim survives verification, and the conclusion still isn't true. Drawn from two decades in the rooms where narratives get built, this field note breaks down four mechanisms — timeline splicing, hindsight as evidence, drift within tolerance, and manufactured confirmation—and how to spot
A "strategic partnership" with no shared platform, no shared roadmap, and no switching cost isn't interdependence — it's a logo slide. Here's how four ride-hailing champions learned that the hard way, and a builder's framework for deciding when to Build, Buy, Borrow, or walk away (Bye).