Matthew: I see a lot of stuff related to developer experience teams being formed at fairly large companies. Why do you think this has become an important topic within the industry now? He says there are two things going on that he sees so one is just a rebranding a slight tweaking of something that's existed for a long time which is dedicated developer productivity teams and infrastructure organizations. Another thing that's really sparking this trend is sort of a burning need like the need for like painkiller level problem around developer experience when it pertains to infrastructure, said Matthew.
Matthew and Luke lead Extend’s Developer Experience team, a team that has approached their work in a way that is more forward-thinking than most. In this episode, they cover how they deliver impact at multiple levels of the organization, their journey with productivity metrics, and how they’ve made DevEx a C-level concern.
Discussion points:
- (1:40) How the DevEx team started and where it fits at Extend
- (5:08) Tradeoffs of DevEx reporting into Platform
- (6:40) The mandate and tasks they focus on
- (12:07) The impact of learning and development efforts
- (16:33) How to drive team-level improvements
- (18:44) Why developer experience is becoming more prevalent
- (26:17) How they made DevEx a C-level concern
- (30:27) Their journey with productivity metrics
- (33:10) Advice for presenting DevEx data to executives
- (34:52) The team’s experience using git metrics tools
- (48:30) Being rigorous in leveraging metrics
Mentions and links:
Connect with Matthew and Luke on LinkedIn
Other podcasts mentioned: Manuel Pais; Peloton’s DevEx survey