Everything I know about good API design

This guide lays out the playbook for running tough, user-first APIs: no breaking changes, stick to familiar patterns, honor long-lived API keys, and make every write idempotent.

It pushes cursor-based pagination for heavy data, rate limits that come with context, and optional fields to keep things lean. Gives GraphQL a side-eye for being heavyweight and pricey to build.

Why it matters: The post tracks a shift in mindset—APIs aren’t just interfaces, they’re infrastructure. Built to last. Easy to adopt. Change carefully, or don’t change at all.