About Me
I work across the stack: event-driven systems, API orchestration, analytics, and AI tooling. I've shipped production software at enterprise scale and built prototypes from scratch at places large and small.
Outside of work, I gravitate toward simulation, distributed infrastructure, and systems that exhibit emergent behavior. I like building things at a scale where the interesting problems start to show up, where naive approaches break and you have to think carefully about architecture.
I'm drawn to the question of how complex systems actually work. The messy reality, not the textbook version. Why do game economies always collapse? Why can't we simulate 302 neurons? What happens when you model political resistance as a feedback loop? I write about these things because working through the ideas publicly makes the thinking sharper.
My approach is simple: pick something interesting, go deep, and build it for real. The actual thing, with all the hard parts included.
I don't learn things by reading about them. I learn by building the real version and hitting every hard problem along the way.
I'd rather build one thing properly than five things halfway. Scale it until the interesting problems show up, then solve those too.
Writing forces clarity. Whether it's a build guide or an essay on why game economies collapse, putting ideas into words reveals what I actually understand.