Hello, World

Every engineer eventually builds their own website. Mine took longer than I'd like to admit.

I graduated from UC Berkeley with a degree in EECS, moved to San Francisco, and joined Meta. Between the chaos of onboarding, ramp-up projects, and learning what it actually means to ship software at the scale of billions of users — writing for the internet kept getting pushed to the bottom of the list.

So here it is. Finally.

Why now

There's a specific kind of knowledge that gets built up over time at a place like Meta — not just technical, but about systems thinking, organizational dynamics, and the tradeoffs that never show up in documentation. A lot of it lives in Slack threads, post-mortems, and late-night debugging sessions. Most of it disappears.

Writing forces clarity. It's easy to think you understand something until you try to explain it to someone else. This site is part of that forcing function.

What I'll write about

A few areas I keep coming back to:

• Systems at scale — distributed systems, infrastructure decisions, and the hidden complexity behind features that look simple from the outside
• ML in production — the gap between a model that works in a notebook and one that runs reliably for millions of people is enormous. I want to talk about that gap.
• Engineering culture — what makes some teams 10x more effective than others, how big tech actually makes decisions, and what I've learned watching great engineers work
• Lessons from big tech — the stuff they don't teach in school or interview prep

I'm not going to pretend I have all the answers. Most of what I write will be half-formed thinking, questions I'm sitting with, and patterns I've noticed. That's the honest version.

One more thing

Sacramento kid, Berkeley grad, now living in SF and working at Meta. If any of that resonates — or if you just want to argue about distributed systems — reach out.

Let's go.