About

Most people stop following a problem when it crosses a boundary. A team, a domain, someone else’s responsibility. I don’t see those boundaries, so I keep following the thread.

That’s how you end up debugging an Erlang memory leak at 2am, or realizing a “simple migration” is actually an organizational fault line, or building governance into type systems because documentation won’t survive contact with reality.

Over 10 years I’ve worked where technology and organization collide: trust & safety at Meta, platform migrations and data foundations at Happening, AI coding agents at Reflection. The common thread isn’t “hard problems”. It’s problems that cross boundaries.

fastpaca

This is my research vehicle. Open source work, writing about what I find, and occasional advisory when the problem is interesting enough.

Working together

I take on a small number of advisory engagements, typically where a technical problem has organizational roots, or vice versa. If you’re not sure which one you have, we should probably talk.