Thirty years building and maintaining distributed systems for banks, airlines, telecoms and games. I’ve watched what fails, and I build what doesn’t.
At a certain size, cloud spend stops being a bill and becomes a system of its own. I get into that system myself, find where the money actually goes, and cut it without slowing anyone down. The savings come from everywhere: rightsizing, autoscaling, finding orphaned services, application tuning and more. For some applications, one percent of CPU savings is worth a million dollars a year. It all adds up.
Governance shouldn’t be a policy document nobody reads. I build it into the tools: a secure agentic platform people can use from their phone or anywhere, usage dashboards that show where AI is landing and where teams need help, and a ready-made AI setup with company tooling built in, so new users are productive on day one.
The best infrastructure is the kind nobody talks about. Today I help lead infrastructure at one of the largest game companies in the world, for games played by hundreds of millions of people, where a bad deploy is front-page news and a good one goes unnoticed. That’s the standard I bring: systems that stay up, stay fast and stay boring.
That game job is full time, so I'm choosy about outside work. I'm remote only, I live outside the USA and Canada (though I can bill from either), and I'm expensive: engagements start at $50,000.
Whatever it is, I can fix it, or at least make it better than what it was.
Still interested? Write to me with:
A longbeard is who you go and find when the obvious fixes have all been tried. I’m still the person people call when no one else can fix it.
When nothing’s on fire, I build apps, websites and games, all the finished ones listed here with their privacy and support pages.