Twenty years in software leaves a particular kind of mark. I started as afull-stack developer, building across industries that had little in common: fleet and job tracking, health IT, enterprise systems. They all shared the same fundamental challenge though, which was distributed data and the infrastructure underneath it. The parts that fascinated me most were never the features. They were the seams between systems and what happened when those seams failed.

That path eventually led to where I am now. I work as a Principal Architectat a cloud-native company, working closely with customers to untangle complex problems and turn them into solutions that actually hold up. A lot of the role is about meeting people where they are: understanding what they're trying to build, what's in the way, and helping them find a path through it. Platform strategy and distributed systems design are still at the core, but the work is as much about people and problems as it is about technology.

Open source is less a preference and more a conviction. The best ideas endure because they're visible, testable, and improvable by anyone. I've contributed where I could and learned far more from reading other people's code than from any course or textbook.

Outside of terminals and architecture diagrams, I tinker withelectronics and robotics. Hardware debugging has a different kind of satisfaction. There is no stack trace, but the smoke tells you everything.

The name day0ops has three readings: