Background

I've spent years building the infrastructure other teams take for granted — CI/CD pipelines, EKS platforms, IaC structures that survive team turnover. The invisible work that determines whether an organization can move or not.

What interests me isn't the stack. It's the layer of decisions underneath it: where complexity accumulates quietly, which platform boundaries create organizational friction, when an infrastructure choice is really a bet on how the team is going to grow.

Those decisions have consequences that don't show up in the sprint where they're made. They show up six months later, when something needs to change and can't.

That's what I write about. For engineering teams and technical leaders navigating those decisions.

If something resonates with a problem you're working through, you can find me on LinkedIn.