DevRel talks

Google's Ray and James argue that developer experience (DX) is 100% about developer productivity and can be measured in terms of value and time.

Denis argues that writing technical articles is one of the few marketing strategies that really adds up over time.

The definition of support is to serve as a foundation for, to sustain without giving way, to undergo or endure, especially with patience.

After five months of working as a developer advocate, Ekene Eze began to question some of the typical ways that DevRel teams measure their success.

Felipe Hoffa introduces how he uses public data sets and the ways that they help him to be more effective.

Learn how three developer marketing campaigns were improved through analysis of quantitative and qualitative metrics.

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.