Since 2010 I've worked as a freelancer, consultant, Head of API, and CTO, for several API-centric technology startups.

Previously at Ride, I was given the chance to work with amazing developers, including several Rails API contributors. We built an event-driven architecture with several REST APIs and a few RPC ones, and it was here I learned the benefits of REST being a state machine over HTTP.

Then at WeWork, I used my experience to help educate developers, define standards for API design and architecture, and work on open-source tooling for OpenAPI, JSON Schema, and HTTP. WeWork has 50+ APIs, and here I have had a chance to learn a lot about keeping distributed applications performant. Timeouts, retries, circuit breakers, keep alive settings, and HTTP caching specificially.

I try to turn all of this learning into books, videos, and articles, so others can learn easily things I've had to learn the hard way.

Articles by Phil