API Design Reviewer's Starter Set
summary
Advocates a repeatable three-stage review lifecycle — early review, solitary deep code review, then a live walk-through and final check — to catch design, security and governance failures before implementation. Requires machine-readable contracts (recommendations: OpenAPI or RAML), automated linting with Spectral and developer-friendly editors like Stoplight Studio, plus a contract repository and written review records. Advises loose governance, a single trusted reviewer over committees, and early involvement of product, dev and consumer representatives so changes remain practical rather than punitive.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:22Why API
- 3:03Character sheets
- 5:46So, why do we need API design reviews?
- 6:29Lifecycle
- 8:42Be exhaustive
- 10:37Make People Talk
- 13:25Fill Your Toolbox
- 14:59Record Everything
- 16:20Govern ... But Not Too Much
- 17:58Teach and Train
- 18:21Rule #4 Train and Teach
- 18:50The End
- 19:20Don't wait until it's too late
- 20:17Be prepared
- 21:27Adopt The Right Mindset
- 22:17API design reviews make everyone grow
related talks
24mThe Augmented API Design Reviewer
36mAPI Governance in an Anti Governance World
25mAutomating API Governance
26mAPI Governance: The Latest Trends Making Teams Love API Standardization.
26mAPI Governance - The Pursuit of Consistency
49mBuilding Software Better: API Lifecycle Management for Developers
24mAugmented API Design Review with OpenAPI and Spectral
24mAPI design is where culture and tech meet each other