How to Properly Craft an AI Product, or What Remains When the Model Catches Up
On building something the baseline cannot replicate.
Read ArticleAs a Software Architecture Lead, I design systems that teams actually want to use. Not architecture that looks impressive in diagrams but falls apart under load, but the kind that makes the right patterns obvious and guides developers toward maintainable solutions.
I focus on building frameworks that scale, making complexity manageable, and ensuring systems still make sense six months later. Before Moxie, I led teams through legacy system redesigns, drastically cut infrastructure costs through better architecture, rewrote critical services for performance, and built real-time collaborative systems at scale.
Good architecture is mostly invisible, it works so well that people forget it exists. That's the goal: systems that feel inevitable because they align with how people actually work.
On building something the baseline cannot replicate.
Read ArticleOr What Remains After Syntax Becomes Cheap.
Read ArticleAn exploration of how technical leadership emerges without formal authority, and why clarity, influence, and the willingness to absorb ambiguity matter more than titles when systems need direction.
Read ArticleA long, spiraling essay about perception, misperception, and the quiet horror of being misunderstood at work, with a few useful truths buried inside.
Read ArticleMore rants about code, systems that actually work, and why your architecture probably doesn't need that abstraction.
Whether it's a technical deep-dive, debating the merits of yet another abstraction, or just geeking out about software - I'm always up for it.