Chris Chabot

I work on what happens when a technical system leaves the team that built it. Outside developers have to understand it, trust it, build with it, and persuade an organisation to adopt it. I led Developer Relations at Google and Twitter, worked on chain infrastructure at Mysten Labs, contributed to Apache and open standards, and still write the code behind the tools I discuss.

An API can be technically sound and still fail because the documentation is poor, local setup is painful, examples teach the wrong things, partners cannot make a business case, or the measurement system cannot distinguish enthusiasm from adoption. Finding and fixing those failures has occupied most of my working life.

At Google+ and Twitter, the work happened at platform scale. At Mysten Labs, it meant helping outside developers make sense of chain infrastructure. Apache and standards work required durable agreements between organisations with different interests. With agent systems, the same work means letting software act on its own without losing the ability to inspect what it did, what evidence it used, or who authorised it.

I am most useful when I can build and explain the product, discover where developers actually get stuck, and carry that evidence back into the engineering and strategy.

Major platform work

Selected work across social platforms, mobile developer ecosystems, identity and API contracts, and chain infrastructure.

Contact

I am based in London. If you are building a developer platform, agent system, or ecosystem and need somebody who can move between code, product, developer experience, and public explanation, I would like to hear about it.

Chris Chabot · London