Introducing Stoplight Platform, built from the ground up to work with your Git repos and workflows. Read the announcement
Phil Sturgeon has been building APIs professionally since 2010. He has worked as an API/architectural consultant for all sorts of companies, from small startups to large organizations like WeWork. He wrote about his experiences in Surviving Other People's APIs and Build APIs You Won't Hate, and grew a community into the largest API-related Slack channel on the internet. Now Phil builds API design tooling at Stoplight, helping with architecture and open-source.
With API descriptions rising in popularity, the main question I hear folks asking about is "API Design-first" or "code-first". This is a bit of a misleading question because these are not two unique things, there are a few variants.
Bundling, dereferencing, and how to use them in Stoplight Studio and CLI workflows.
A look at the ways companies use and support open-source projects.
Ask 100 developers where a semicolon should go, and you'll either get 100 answers, or a all-on-all fist fight. To save this from happening at work, most folks implement a style guide, which beyond helping with consistent style to avoid new developers getting shouted at for "doing it wrong".