Twenty-nine years on the other side of the outage.
Every system fails eventually. The only question is whether you find out before your customers do. I've spent 29 years making sure the answer is yes.
It started with access gates, payment terminals and wireless networks at a busy ski resort — downtime there means thousands of people stuck in the cold. Then hospital laboratories, where downtime means samples that can't wait. Then a cable operator's call-center platform: 200 servers that had to answer every call, every day, no excuses.
That was the training. Since 2016 I've been building the systems themselves: eight years in blockchain engineering, three as CTO at Woonkly shipping live DeFi — swaps, farms, staking — under real market pressure. More recently I co-built a Rust engine that cut cloud compute costs 40–60% while holding latency under 15 milliseconds. It runs today on Azure and AWS.
Operations teaches you how systems break. Writing the code teaches you why. I do both.
