This is a weekly podcast focused on developer productivity and the teams and leaders dedicated to improving it. Topics include in-depth interviews with Platform...
Rethinking developer experience at T-Mobile: DevEx vs devprod, exec buy-in, and developer self-service
Chris Chandler is a Senior Member of the Technical Staff for Developer Productivity at T-Mobile. Chris has led several major initiatives to improve developer experience including their internal developer portal, Starter Kits (a patented developer platform that predates Backstage), and Workforce Transformation Bootcamps for onboarding developers faster.Mentions and links:Follow Chris on LinkedInMeasuring developer productivity with the DX Core 4Listen to Decoder with Nilay Patel.Discussion points:(0:47) From developer experience to developer productivity(7:03) Getting executive buy-in for developer productivity initiatives(13:54) What Chris’s team is responsible for(17:02) How they’ve built relationships with other teams(20:57) How they built and got funding for Dev Console and Starter Kits(27:23) Homegrown solution vs Backstage
--------
31:56
DX Core 4: 2024 benchmarks
In this episode, Abi and Laura dive into the 2024 DX Core 4 benchmarks, sharing insights across data from 500+ companies. They discuss what these benchmarks mean for engineering leaders, how to interpret key metrics like the Developer Experience Index, and offer advice on how to best use benchmarking data in your organization. Mentions and Links:DX core 4 benchmarksMeasuring developer productivity with the DX Core 4Developer experience index (DXI)Will Larson’s article on the Core 4 and power of benchmarking dataDiscussion points:(0:42) What benchmarks are for(3:44) Overview of the DX Core 4 benchmarks(6:07) PR throughput data (11:05) Key insights related to startups and mobile teams (14:54) Change fail rate data (19:42) How to best use benchmarking data
In this episode, Abi and Laura introduce the DX Core 4, a new framework designed to simplify how organizations measure developer productivity. They discuss the evolution of productivity metrics, comparing Core 4 with frameworks like DORA, SPACE, and DevEx, and emphasize its focus on speed, effectiveness, quality, and impact. They explore why each metric was chosen, the importance of balancing productivity measures with developer experience, and how Core 4 can help engineering leaders align productivity goals with broader business objectives. Mentions and Links:Measuring developer productivity with the DX Core 4Laura’s developer productivity metrics courseDiscussion Points:(2:42) Introduction to the DX Core 4(3:42) Identifying the Core 4's target audience and key stakeholders(4:38) Origins and purpose(9:20) Building executive alignment(14:15) Tying metrics to business value through output-oriented measures(24:45) Defining impact(32:42) Choosing between DORA, SPACE, and Core 4 frameworks
--------
36:59
SPACE framework, PRs per engineer, AI research
In this episode, Brian Houck, Applied Scientist, Developer Productivity at Microsoft, covers SPACE, DORA, and some specific metrics the developer productivity research team is finding useful. The conversation starts by comparing DORA and SPACE. Brian explains why activity metrics were included in the SPACE framework, then dives into one metric in particular: pull request throughput. Brian also describes another metric Microsoft is finding useful, and gives a preview into where his research is heading. Mentions and linksConnect with Brian on LinkedInThe SPACE of Developer Productivity: There's More to It Than You ThinkMeasuring developer productivity with the DX Core 4DevEx in actionDORA, SPACE, and DevEx: Which framework should you use?Discussion points(0:48) SPACE framework's growth and adoption(3:47) Comparing DORA and SPACE(6:30) SPACE misconceptions and common implementation challenges(9:34) Whether PR throughput is useful (15:13) Real-world example of using PR throughput (21:33) Talking about metrics like PR throughput internally (24:39) Where Brian’s research is heading
--------
32:14
CTO buy-in, measuring sentiment, and customer focus
Click here to view the episode transcript.
In this episode, Snowflake’s Gilad Turbahn, Head of Developer Productivity, and Amy Yuan, Director of Engineering, dive into how they elevated developer productivity to a top company priority. They discuss the pivotal role of Snowflake’s CTO, who personally invested over half his time to guide the initiative, and how leadership's hands-on involvement secured buy-in across teams. The conversation also explores the importance of collaboration between engineering and product management, and how measuring user sentiment helped them deliver meaningful, long-lasting improvements.Mentions and linksConnect with Gilad and Amy on LinkedInMeasuring developer productivity with the DX Core 4Discussion Points(0:48) The need for a shift at Snowflake(3:59) Leadership involvement and prioritization of developer productivity(8:56) The partnership between engineering and product managers(20:01) From feature factory to customer outcome-focused development(27:36) Shifting measurement focus to user sentiment and customer outcomes(39:13) Gaining buy-in for sentiment metrics and tying them to business impact(51:11) How Snowflake’s CTO and volunteers accelerated developer productivity improvements.
This is a weekly podcast focused on developer productivity and the teams and leaders dedicated to improving it. Topics include in-depth interviews with Platform and DevEx teams, as well as the latest research and approaches on measuring developer productivity. The EE podcast is hosted by Abi Noda, the founder and CEO of DX (getdx.com) and published researcher focused on developing measurement methods to help organizations improve developer experience and productivity.