Collaboration & Productivity-Missing Links in API Development
summary
Explains concrete fixes for API team friction: use workspaces to group people and resources, surface changes via activity logs and changelogs, and run version control for rollbacks; apply role-based access control to prevent mistakes; use comments and annotations for pinpoint feedback; enforce governance by calling the Postman API (OpenAPI 3.0 + Newman in CI) to check naming, tests and specs; public workspaces get automated secret-scrubbing. Describes evolution from exported files to shared team libraries to scalable public collaboration.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:12Agenda
- 1:50How APIs are developed
- 3:19Power of APIs
- 4:31Bounded Context
- 5:20APIs are not technical
- 6:10The Bounded Cortex
- 7:49Solutions
- 8:44What is Collaboration
- 10:51Workspaces
- 11:56Shared Context
- 13:17Visible Action
- 14:33Communication
- 15:33Access Control
- 16:12Collaboration
- 17:00Economic Benefits
- 17:26Conclusion
- 18:09Questions
- 18:27Evolution of Collaboration
- 19:02Stages of Collaboration
- 21:16Collaboration Security
- 23:04Motivation for Client Devs
- 24:57Challenges of Public Collaboration
- 26:21Small Teams
related talks
22mRevolutionizing API development: Collaborative workflows with Postman
25mPostman Session: Supercharge API Collaboration With Postman
28mOptimizing the developer experience through collaboration
40mWhen documenting is designing
22mBeyond the Spec: Making OpenAPI More Human
25mTackling OpenAPI Drift
35mMastering API Ops: Build Scalable Applications
49mBuilding Software Better: API Lifecycle Management for Developers