016a: How to measure success in your DX

Jul 2, 2024

Developer Advocate Beppe Catanese from Adyen discusses automating developer experience, API tooling, SDK generation, open API pipeline, and measuring success. They explore balancing privacy concerns, contributing to the OpenAPI Generator Project, validating source webhooks, and challenges in the project with new API flow specification.

Ask episode

Chapters

Transcript

Episode notes

Intro

00:00 • 3min

Enhancing Developer Experience through API Tooling and Automation

03:00 • 26min

Exploring Methods for Measuring Tool Usage and Balancing Privacy Concerns

28:48 • 2min

Contributing to the OpenAPI Generator Project

30:50 • 5min

Working with Webhooks and Creating Signatures for Validating Source

35:52 • 3min

OpenAPI Generator Project Challenges and New Specification Introduction

39:02 • 10min

Replacement episode to fix missing audio.

Developer Advocate Beppe Catanese from the Dutch payment company Adyen joins me. Over the past decade, Adyen has been expanding globally. Beppe and I will discuss the internal pipeline built at Adyen to automate the creation of a world-class developer experience. Beppe also shares his work in open source and how Adyen measures the success of their DX.

Adyen Developer Portal

Brought to you by APIMatic

Questions Beppe answers in this episode

Tell us about your career that lead to working in developer experience at Adyen

What have you observed in the evolution of developer experience around APIs?

When it comes to SDKs, do you have an engineering team creating those by hand or auto generating them?

How are changes to your OpenAPI definition managed as part of your pipeline or workflow?

Do you have contract testing as part of your pipeline?

Is your team writing tests or generating them for each SDK that is produced from the pipeline?

How many people are working to maintain the OpenAPI SDK pipeline you've built?

You have many teams feeding APIs into a unified developer experience?

How do you go about discovering OpenAPI tools, do you use Open source or build your own?

Do you open source your SDKs?

Are there any challenges taking contribution to your open source SDKs when parts are generated?

How are you measuring the benefits and return on investment for building a good developer experience, documentation, SDKs and tools?

Are you using anything to measure the usage of tools and SDKs?

How did you get involved contributing to OpenAPI Generator project and what was that experience like for you?

Did you work on OpenAPI generator's core engine in Java or the mustache templates which controlled the output for each programming language?

Where you generating the server code to dispatch webhooks or the client code to receive?

Is OpenAPI helping standardize how companies are implementing webhooks so they are easier for developers to consume?

Should developers be concerned that OpenAPI Generator has over 4000 open issues and over 400 Pull requests?

What are OpenAPI Workflows and how will developers benefit from them?