Hello World — Why I'm Writing
Why I built this site, who it's for, and what I plan to write about.
I’ve been meaning to build a personal site for years.
The excuse was always the same: I’ll do it when I have something worth saying. Turns out that’s backwards. You find out what you have to say by writing. So here we are.
Why Now
Three things converged:
One: I’m building Protops on the side — a lightweight ops tool for product-minded people — and I kept forming opinions I wasn’t publishing anywhere. That’s a waste.
Two: I’ve been leading One Pipeline at Capital One for a few years now. I’ve accumulated a lot of hard-won knowledge about platform teams, developer experience, and what it actually looks like to do PM on internal infrastructure. Most of that knowledge lives in Slack threads, retro docs, and my own head. It shouldn’t.
Three: I decided that thinking in private is wasteful. Writing forces clarity. Publishing creates accountability. If I’m wrong about something, I’d rather find out.
What I’ll Write About
Three buckets, roughly:
Platform & developer experience — What it actually looks like to build internal tooling at scale. The organizational dynamics, the adoption challenges, the metrics that matter versus the ones that feel good on a slide. Most content on DevEx is either too abstract (“just measure developer happiness!”) or too tactical (benchmarking survey #802). I want to write the stuff in between.
Product strategy — I think deeply about how strategy translates into product decisions: OKRs that don’t collapse into vanity metrics, roadmaps that reflect actual tradeoffs, how platform teams define “the customer” when everyone is a customer. Expect opinionated takes.
Building in public — Protops is a real thing I’m trying to build while working a full-time job. I’ll write about that honestly — what’s working, what isn’t, and what I’m learning about going from PM to founder.
A note on tone
I write the way I talk: direct, a little informal, and with a lot of opinions. If you’re looking for thought leadership content that hedges every claim, this probably isn’t your spot. If you want unfiltered takes from someone who’s been in the room — welcome.
Who This Is For
Probably: product managers who care about technical systems. Engineers who are moving toward product. Leaders building internal platforms. People who’ve sat through one too many “developer experience” talks that said nothing actionable.
If that’s you — welcome. Let’s see where this goes.