Скачать или смотреть Keeping Devs Happy Through API Change Management

In this POST/CON 25 session, Michael McGovern, Developer Advocate at Paddle, shares three critical lessons that turned their change log into their most powerful technical marketing asset.

Key Topics Covered:
API change management best practices and strategic implementation
API documentation that speaks your customers' language and drives adoption
Change log optimization for both technical implementation and business value
Multi-channel communication strategies using Postman, Slack, and email
Postman API Network integration for automated change notifications
Real-world metrics: doubled collection forks and increased workspace views

What You'll Learn:

How to create change logs that serve as technical marketing assets
The "why" behind API changes, not just the "what"
Effective communication channels for reaching developers and decision makers
Using Postman workspace updates for visual, SEO-optimized change communication
Building modular change management systems that scale with your API
Converting change logs into sales tools for pre-commitment conversations
= Starting small with simple tools (even markdown files) and iterating effectively

00:00 Introduction
01:07 The Power of Change Logs
01:42 Three Key Lessons Preview
02:39 Change Management as Developer Experience
04:11 Lesson 1: Speaking the Customers' Language
05:35 Lesson 2: Effective Change Communication
06:23 Postman Integration Strategy
07:48 Lesson 3: Start Small and Build Modular
08:27 Real-World Impact and Results
12:10 Advice for Getting Started