DevRel talks

Melissa and Adam discuss concrete examples of how to measure: 1) evangelist/advocate engagement with developers 2) composite measures of Open Source project health and 3) program impact estimations using synthetic control groups.

Starting from scratch with metrics can feel overwhelming. Jason shares practical insights from his journey, highlighting how to build foundational reports and gather early insights to track DevRel efforts effectively.

Creating an inspiring and beneficial journey for developers who engage with your product is essential for a smooth onboarding.

Travel has typically been a big part of developer relations.

How should we serve non-developers when building developer portals, documentation, and other aspects of developer experience?.

Erin introduces five things you can do to model good documentation practice for your community and grow a culture of documentation among developers.

Aman shares the ways that he discovered, learned, and continues to practice to become better at public speaking, presentation deck making, and delivering talks.

Alexandra describes a scalable onboarding process for bringing on one new engineer or fifty to your project.

If a developer says that our product has increased their productivity, should we take their word for it?

Choosing the right metrics to measure and prove the value of DevRel isn’t always an easy thing to do.

Once you've defined your dev rel team's KPIs, how can you keep track of your progress?

How does developer relations apply to people who don't think of themselves as developers? As APIs become available to people who are less technical than traditional developers, Joyce Lin looks at what this means for dev rel.