API Code First vs Design First
summary
Argues that open api design‑first then evolve‑with‑code beats ad‑hoc code‑first: use OpenAPI to generate mock servers and docs, reuse the YAML for request validation (Committee/Dredd‑style middleware) and keep one source of truth. Reports a 300‑person poll with 35.5% mixed workflows, ~20–21% fully design‑first and ~20% adopting it. Describes a built prototype that clones repos, converts specs to OpenAPI v3, creates mocks, reference docs, SDKs and Postman collections — it works and drastically reduces wasted coding.
AI-written summary · about
chapters (5)
- 0:00Start
- 5:59ANNOTATIONS OR YAML?
- 8:08CODE FIRST VS DESIGN FIRST
- 22:17API DESCRIPTION LINTING
- 26:07REUSE API DESCRIPTIONS FOR VALIDATION
related talks
25mThe Life Changing Magic of Becoming API First
20mUsing Design First to superpower your app development
43mWhy You Should Be Doing Contract-First Development
05mAPI-First Development: Future-Ready Systems
30mHow to Win Friends with API First
18mPrototype-first - a modern API development workflow
47mDesign First: OpenApi and AsyncApi in Action!
49mPoor API design is not sustainable.