70 avsnitt • Längd: 45 min • Månadsvis
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.
The podcast Engineering Enablement by Abi Noda is created by DX. The podcast and the artwork on this page are embedded on this page using the public podcast feed (RSS).
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:
Discussion points:
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:
Discussion Points:
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 links
Discussion points
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 links
Discussion Points
Click here to view the episode transcript.
In this episode, Emanuel Mueller Ramos, Head of Developer Experience at Skyscanner, discusses the evolution of his team as they transitioned from focusing on frameworks and middleware to becoming a customer-centric, impact-driven organization. Emanuel details the strategies he used to gain stakeholder buy-in, why it's crucial to rethink traditional productivity metrics, and how they made a cultural shift to prioritize developer happiness and effectiveness. This conversation highlights the steps necessary to build a developer experience function that delivers meaningful impact.
Mentions and links:
Discussion points:
Click here to view the episode transcript.
In this week's episode, Abi is joined by industry leaders Idan Gazit from GitHub, Anna Sulkina from Airbnb, and Alix Melchy from Jumio. Together, they discuss the impact of GenAI tools on developer productivity, exploring challenges in measurement and enhancement. They delve into AI's evolving role in engineering, from overcoming friction points to exploring real-world applications and the future of technology. Gain insights into how AI-driven chat assistants are reshaping workflows and the vision for coding.
Links:
Timestamps:
Click here to view the episode transcript.
In this week's episode, Abi welcomes Jared Wolinsky, Vice President of Platform Engineering at SiriusXM, to delve into the inner workings of platform engineering at SiriusXM. Jared sheds light on their innovative approach to prioritizing projects, emphasizing alignment with overarching business goals. They explore how these strategies boost developer speed and drive technological advancement within the organization.
Links:
Timestamps:
Click here to view the episode transcript'.
In this episode, Michelle Swartz, Vice president of Developer Enablement American Express, shares insights on improving developer experience. She discusses the creation of an onboarding bootcamp and the development of the AmEx Way Library for better knowledge management. Michelle explains how AmEx balances standardization and flexibility with the concept of Paved Roads. She also highlights the importance of measuring success, fostering community, and elevating the company's tech credibility.
Mentions and links
Timestamps
Click here to view the episode transcript'.
This week’s episode is a recording from a recent event hosted by Abi Noda (CEO of DX) and Laura Tacho (CTO at DX). The episode begins with an overview of the DORA, SPACE, and DevEx frameworks, including where they overlap and common misconceptions about each. Laura and Abi discuss the advantages and drawbacks of each framework, then discuss how to choose which framework to use.
Mentions and Links:
Discussion points:
Click here to view the episode transcript.
In this week's episode, we welcome Derek DeBellis, lead researcher on Google's DORA team, for a deep dive into the science and methodology behind DORA's research. We explore Derek's background, his role at Google, and how DORA intersects with other research disciplines. Derek takes us through DORA's research process step by step, from defining outcomes and factors to survey design, analysis, and structural equation modeling.
Mentions and Links:
Discussion points:
Click here to view the episode transcript.
This week we’re joined by Sean Mcllroy from Slack’s Release Engineering team to learn about how they’ve fully automated their deployment process. This conversation covers Slack’s original release process, key changes Sean’s team has made, and the latest challenges they’re working on today.
Mentions and links:
Time Stamps:
Click here to view the episode transcript.
This week’s episode is the recording of a live conversation between Abi and Chris Westerhold (Thoughtworks Head of Developer Experience). This conversation is useful for anyone early in their journey with developer portals or platforms: Abi and Chris discuss common approaches to solving these problems, pitfalls to avoid, building vs. buying, and more.
Mentions and Links
Time Stamps:
Click here to listen to the episode transcript.
On this week's episode, Abi interviews Kent Wills, Director of Engineering Effectiveness at Yelp. He shares insights into the evolution of their developer productivity efforts over the past decade. From tackling challenges with their monolithic architecture to scaling productivity initiatives for over 1,300 developers. Kent also touches on his experience in building a business case for developer productivity.
Discussion points:
Mentions and Links
This week we’re joined by Gail Carmichael, Principal Instructional Engineer at Splunk. At Splunk, Gail’s team is responsible for improving developer onboarding, which they do through a multi-day learning program. Here, Gail shares how this program works and how they measure developer onboarding. The conversation also covers what instructional engineers are generally, and how Gail demonstrates the impact of her team’s work.
Discussion points:
Mentions and Links
In this episode we’re joined by Adam Rogal, who leads Developer Productivity and Platform at DoorDash. Adam describes DoorDash’s journey with their internal developer portal, and gives advice for other teams looking to follow a similar path. Adam also describes how his team delivered value quickly and drove adoption for their developer platform.
Discussion points:
Mentions and links:
In this episode, Abi has a fascinating conversation with Rebecca Parsons, ThoughtWorks's CTO, Camilla Crispim, and Erik Dörnenburg on the ThoughtWorks Tech Radar. The trio begins with an overview of Tech Radar and its history before delving into the intricate process of creating each report involving multiple teams and stakeholders. The conversation concludes with a focus on the evolution of Tech Radar's design and process and potential future changes. This episode offers Tech Radar fans an exclusive behind-the-scenes look at its history and production.
Discussion points:
Mentions and links:
This week's guest is Eirini Kalliamvakou, a staff researcher at GitHub focused on AI and developer experience. Eirini sits at the forefront of research into GitHub Copilot. Abi and Eirini discuss recent research on how AI coding assistance impacts developer productivity. They talk about how leaders should build business cases for AI tools. They also preview what's to come with AI tools and implications for how developer productivity is measured.
Discussion points:
Mentions and links:
Christopher Sanson is a product manager at Airbnb who is dedicated to enhancing developer productivity and tooling. Today, we learn more about Airbnb's developer productivity team and how various teams use metrics, both within and outside the organization. From there, we dive even deeper into their measurement journey, highlighting their implementation of DORA metrics and the challenges they overcame throughout the process.
Discussion points:
Mentions and links:
In this episode, Abi speaks with Ana Petkovska, who is currently leading the developer experience team at Nexthink. Ana takes us through her journey of leading a DevOps team that underwent multiple transformations. She explains how her team went from being a DevOps team to EngProd and eventually DevEx. Ana elaborates on her team's challenges and the reasons behind the shift in focus. She also shares how she discovered EngProd and used data from companies like Google to convince her company to invest in EngProd. Finally, Ana explains how DevEx came into the picture and changed how her team approaches and measures their work.
Discussion points:
Mentions and links:
In this episode, Abi chats with Grant Jenks, Senior Staff SWE, Engineering Insights @ LinkedIn. They dive into LinkedIn's developer insights platform, iHub, and its backstory. The conversation covers qualitative versus quantitative metrics, sharing concerns about these terms and exploring their correlation. The episode wraps up with technical topics like winsorized means, thoughts on composite scores, and ways AI can benefit developer productivity teams.
(1:10) Insights in the productivity space
(7:13) LinkedIn's metrics platform, iHub
(12:52) Making metrics actionable
(15:35) Choosing the right and wrong metrics
(19:39) The difficulty of answering simple questions
(26:23) Top-down vs. bottom-up approach to metrics
(32:12) Winsorized mean and selecting measurements
(39:25) Using composite metrics
(46:57) Using AI in developer productivity
This week's episode is with Jim Beyers, VP of Engineering Enablement at CVS Health. Jim joined CVS a year ago to lead an effort to build an internal developer platform. Abi and Jim discuss how Jim joined CVS to build an internal developer platform, what brought him to the job, and how the developer experience fits into the broader transformation goals of CVS. Additionally, this episode covers building the team, defining a strategy, and how he's thinking about winning the hearts and minds across his organization.
Discussion points:
Mentions and links:
This week we spoke with Nils Loodin, Platform Product Manager at Spotify. Nils describes how his role in platform product management works, including unique challenges, approaches, and career considerations. Nils also discusses some of the recent changes within Spotify's platform organization, including shifting teams from tech-centric to journey-centric.
Discussion points:
Mentions and links:
This week we’re joined by Justin Wright and Matthew Dimich, who lead Platform Engineering and Engineering Enablement at Thomson Reuters. Justin and Matt give an inside look at how they’ve evolved their organization’s structure and approach over the past 8 years.
Discussion points:
Mentions and links:
This week’s episode dives into the DORA research program and this year’s State of DevOps Report. Nathen Harvey, who leads DORA at Google, shares the key findings from the research and what’s changed since previous reports.
Discussion points:
Mentions and links:
This week we’re joined by Preeti Kota, the Head of Engineering for Compass at Atlassian. Preeti walks us through Atlassian’s journey with developer experience: including how they measure DevEx, and how they drive improvements through efforts at both the organization and team levels. Preeti also talks about how this journey has led to the development of Atlassian’s newly released internal developer portal, Compass.
Mentions and links:
Discussion points:
This week we’re joined by Mark Côté, who leads the Developer Infrastructure organization at Shopify, to learn about their developer survey program. Mark shares what went into designing and running the survey, what they’ve done to drive participation rates higher, and how they interpret their data.
Mentions and links:
Discussion points:
Thomas Khalil, Head of Platform and SRE at Trivago, describes how the teams reporting into him are structured, the tactics they’re using to increase awareness of their work, and how they demonstrate their impact.
Discussion points:
Mentions and links:
Connect with Thomas on LinkedIn
This week’s guest is Jenny McClain, who leads R&D Team Enablement at Toast. Jenny’s team focuses on enabling individual teams at Toast to drive their own productivity improvements, and this conversation dives into how they tackle this problem.
Discussion points:
Mentions and links:
Follow Jenny on LinkedIn
Tuckman’s stages of group development
Working Agreements template from Steve Sobel, Director of Engineering at Toast - one of the resources featured in Toast’s Team Health Toolkit
This week we’re joined by Ciera Jaspan and Collin Green, who lead the Engineering Productivity Research team at Google. Ciera and Collin have written several papers from studies they’ve conducted, and this discussion covers the insights from their research as well as their work more broadly at Google.
Discussion points:
Mentions and links:
Follow Ciera and Collin on LinkedIn
A Human-Centered Approach to Measuring Developer Productivity - Paper, Abi’s summary
Enabling the Study of Software Development with Cross-Tool Logs - Paper
Defining, Measuring, and Managing Tech Debt - Paper, Abi’s summary
Google’s Goals, Signals, Metrics framework - Paper, Abi’s summary
This week we’re joined by Jason Kennedy, Senior Engineering Manager of Developer Experience at One Medical. Jason’s team takes a uniquely customer-driven approach to improving the developer experience, and in this episode he describes their philosophy and how it works in practice. Jason explains how they shadow developers, how they run surveys, and more.
Discussion points:
Mentions and links:
Follow Jason on LinkedIn
Listen to the podcast episode with Jasmine James
Book about Disney: Be Our Guest
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:
Mentions and links:
Connect with Matthew and Luke on LinkedIn
Other podcasts mentioned: Manuel Pais; Peloton’s DevEx survey
Manuel Pais delves into one of the concepts covered in his book “Team Topologies”: platform and enabling work. Manuel shares how he views the strategy behind when and how to invest in platform or enabling work. This conversation also goes into each type of work in more detail, covering topics such as measuring cognitive load and where platform engineering may be heading in the future.
Thansha Sadacharam, who leads Tech Learning and Insights at Peloton walks us through the journey of building the company’s developer experience survey. She shares what went into the survey’s design, rollout, and maintenance, as well as the different teams involved.
Discussion points:
Mentions and links
Follow Thansha on LinkedIn
In this episode, Abi is interviewed by Laura Tacho about the new paper he co-authored with Dr. Nicole Forsgren, Dr. Margaret-Anne Storey, and Dr. Michaela Greiler. Abi and Laura discuss the pitfalls of some of the common metrics organizations use, and how the new paper builds on prior frameworks such as DORA and SPACE to offer a new approach to measuring and improving developer productivity.
Discussion topics:
Resources for learning more about the DevEx framework:
Read the new paper on ACM Queue
Read Abi’s announcement about the new paper
Read how top companies measure developer productivity
Connect with Abi and Laura
Sign up for Laura’s course, Measuring Development Team Performance
Connect with Laura on LinkedIn or Twitter
Connect with Abi on LinkedIn or Twitter
Tara Hernandez, the VP of Developer Productivity at MongoDB, joins the podcast to give an inside look at what the developer experience looks like at an organization that develops a database. Here, Tara shares what it looks like to develop, test, and release changes at MongoDB, while also providing insight into how the company invests in developer productivity more broadly.
Discussion points:
Mentions and links:
Follow Tara on LinkedIn or Twitter
Read more about MongoDB’s “Evergreen” Continuous Integration
Visit MongoDB’s engineering blog
Max Kanat-Alexander, the Tech Lead for the Developer Productivity and Insights Team at LinkedIn, shares an inside look at LinkedIn’s metrics platform and how teams across the organization use it.
Discussion points:
Mentions and links:
Connect with Max on LinkedIn or Twitter
Read the article, Measuring Developer Productivity and Happiness at LinkedIn
Listen to the first interview with Max and his colleague Or Michael Berlowitz: Episode 23
Abi’s blog post on the Three-Bucket Framework for Engineering Metrics
Mike Fisher, the former CTO at Etsy, spearheaded a multi-year developer experience initiative aimed at improving developer happiness and efficiency during his time at Etsy. Here, he shares the story of that initiative, including the pillars of the program and the investment that went into it. Towards the end of the conversation, Mike also shares his perspective on measuring developer productivity.
Discussion points:
Mentions and links:
Follow Mike on LinkedIn or Twitter
Subscribe to Mike’s newsletter, Fish Food for Thought
Karl’s team at American Airlines were early adopters of Backstage, and in this episode he shares their journey of implementing and rolling out a developer portal. He also describes two of the extensions his team has built for their portal.
Discussion points:
Mentions and links:
Follow Karl on LinkedIn
The Runway platform at American Airlines
Read more on the engineering blog from American Airlines
As product lead, Russ Nealis has been focused on introducing the discipline of product management in the Developer Foundations organization. This episode discusses the reasons why PMs are currently uncommon in platform organizations, examples of when having a PM has been helpful, and more.
Discussion points:
Mentions and links:
Follow Russ on LinkedIn
Episode 7 with Will Larson - related to why it’s difficult to find Platform PMs
Episode 27 with Jean-Michel Lemieux - related to the percentage of investment that should be put towards platform investments
The Build Trap by Melissa Perri
Ask Your Developer by Jeff Lawson
In this deep-dive episode, Brian Scanlan, Principal Systems Engineer at Intercom, describes how the company’s on-call process works. He explains how the process started and key changes they’ve made over the years, including a new volunteer model, changes to compensation, and more.
Discussion points:
Mentions and links:
Jack Li explains how his production engineering team rolled out a new incident review process, how they’ve made the case for investing in reliability, and specific tools his team has built to improve reliability.
—
Discussion points:
—
Mentions and links:
Follow Jack on LinkedIn
Jack’s article from his time on Shopify about their Merge Queue
Jack’s talk on Shopify’s Merge Queue at GitHub Universe 2019
Nathen Harvey, who leads DORA at Google, explains what DORA is, how it has evolved in recent years, the common challenges companies face as they adopt DORA metrics, and where the program may be heading in the future.
—
Discussion points:
(1:48) What DORA is today and how it exists within Google
(3:37) The vision for Google and DORA coming together
(5:20) How the DORA research program works
(7:53) Who participates in the DORA survey
(9:28) How the industry benchmarks are identified
(11:05) How the reports have evolved over recent years
(13:55) How reliability is measured
(15:19) Why the 2022 report didn’t have an Elite category
(17:11) The new Slowing, Flowing, and Retiring clusters
(19:25) How to think about applying the benchmarks
(20:45) Challenges with how DORA metrics are used
(24:02) Why comparing teams’ DORA metrics is an antipattern
(26:18) Why ‘industry’ doesn’t matter when comparing organizations to benchmarks
(29:32) Moving beyond DORA metrics to optimize organizational performance
(30:56) Defining different DORA metrics
(36:27) Measuring deployment frequency at the team level, not the organizational level
(38:29) The capabilities: there’s more to DORA than the four metrics
(43:09) How DORA and SPACE are related
(47:58) DORA’s capabilities assessment tool
(49:26) Where DORA is heading
—
Mentions and links:
Follow Nathen on LinkedIn or Twitter
Engineering Enablement episode with Dr. Nicole Forsgren
Bryan Finster’s How to Use & Abuse DORA Metrics (and Abi’s summary of the paper)
Engineering Enablement episode with Dr. Margaret-Anne Storey
Join the DORA community for discussion and events: dora.community
This week's guest is Dr. Margaret-Anne Storey, who goes by the name Peggy. Peggy is a professor of Computer Science at the University of Victoria, the Chief Scientist at DX, and co-author of the SPACE Framework, which is the topic of focus in this episode. Today’s conversation discusses what the SPACE framework is and what went into developing the metrics and categories. Peggy also shares where she sees this line of research heading next.
—
Discussion points:
(1:29) Peggy’s background
(4:01) What the SPACE framework is
(5:55) Why the researchers came together for this paper
(7:27) The process of writing this paper
(9:52) How the SPACE categories and acronym emerged
(11:50) The authors’ intention for how this framework would be received
(13:26) Finding a definition for what developer productivity is
(17:08) The metrics included in the SPACE framework
(24:48) How SPACE is different from DORA
(26:17) Why lines of code and number of pull requests were included as example metrics
(27:14) What Peggy is thinking about next
—
Mentions and links:
Where to find Peggy: Twitter, Website
The SPACE of Developer Productivity: There’s more to it than you think by Nicole Forsgren, Margaret-Anne Storey, Chandra Madilla, Thomas Zimmerman, Brian Houck, and Jenna Butler
Abi’s summary of the SPACE paper
Peggy’s talk, What Does Productivity Actually Mean for Developers?
This week’s guest is Jeremiah Lee, who was previously a manager at Stripe and product manager at Spotify. This conversation focuses on org structure, and specifically Jeremiah’s experience with the popular squad model from Spotify. Jeremiah provides the backstory on where the model came from, what parts of the model were a challenge, and advice for leaders either already adopting the model or considering doing so.
Discussion points:
(1:40) What the Spotify model is
(4:39) Jeremiah’s impression of the Spotify model as he joined the company
(7:29) Spotify’s progress in adopting the model as Jeremiah joined
(9:55) Challenges with matrix management
(12:02) The role of engineering managers
(14:40) What the model was designed to solve
(15:54) Good autonomy versus toxic autonomy
(18:51) How Agile coaches were used at Spotify
(21:39) Advice for teams who are struggling to implement the Spotify model
(24:50) Advice for leaders who are starting to think about org design
(27:30) How Stripe approached org structure
(30:26) How org structure affects a platform team’s work
(33:32) Tracking engineering org structures
(36:02) Why the squad model became so popular
(39:37) What the original authors may have felt about the popularity of the model
Mentions and links:
Follow Jeremiah on LinkedIn
Jeremiah’s Spotify’s Failed #SquadGoals
The original whitepaper on the Spotify model: Scaling Agile at Spotify
Team Topologies by Matthew Skelton and Manuel Pais
Essential Scrum by Kenneth S. Rubin
Jean-Michel Lemieux, former CTO of Shopify and VP of Engineering at Atlassian, explains how to advocate for investing in platform work, which projects to fund, and what distinguishes a great platform leader.
—
Discussion points:
(1:38) Jean-Michel’s definition of platform work
(6:44) Why reliability, performance, and stability do fall within platform work
(7:24) The consequences of lacking a product mindset in platform
(9:20) Why and how to advocate for investing 50% of R&D spend in platform work
(12:31) How Jean-Michel arrived at 50% as the percentage of R&D spend that should be allocated to platform
(16:09) Jean-Michel’s experiences with different levels of investment in platform work
(21:59) What percentage of platform investment should go towards keep the lights on work
(24:01) Whether the allocation changes at different company stages
(27:05) Why platform work is consistently underinvested in
(29:00) Why having a platform team could be an anti-pattern
(32:32) How to advocate for this work to leaders
(35:35) What it looks like to over-invest in platform work
(40:03) How to decide which initiatives to invest in
(47:41) Making build vs buy decisions in platform work
(49:58) What distinguishes a great platform leader
—
Mentions and links:
Follow Jean-Michel Lemieux on LinkedIn and Twitter
Abi’s post that sourced many of the questions discussed in this conversation
Jean-Michel’s book chapter on platform investments
Jean-Michel’s definition of what platform work is
The podcast episode on what Shopify expects of managers
Jonathan Biddle, Director of Engineering Effectiveness at Wayfair, shares the story of how his team found repeat success and subsequently grew in size and scope. He shares lessons they’ve borrowed from startups, including understanding the adoption curve and knowing your core users, and offers advice for other platform teams looking to move to the next stage.
—
Discussion points:
(01:15) How Jonathan moved into his role
(05:30) Why Platforms teams are in a position of leverage, but also ambiguity
(07:18) The initial work Jonathan’s team focused on
(10:07) Creating transactional versus recurring value
(11:36) The difference between startups and platform teams
(14:12) Expanding the team’s scope and rebranding to Developer Acceleration
(18:20) What drove the platform team’s success
(21:05) Three adoption concepts to understand
(24:41) Knowing your core customers
(27:36) Adoption metrics and feedback gathering mechanisms
(33:37) When to mandate adoption or rely on organic adoption
(38:38) A story of when adoption fell short
(45:35) Advice for how other teams can go from zero to one
—
Mentions and links:
Follow Jonathan on LinkedIn
Diffusion of Innovations by Everett M. Rogers (and the Wikipedia page for the book)
Crossing the Chasm by Geoffrey A. Moore
Let My People Go Surfing by Yvon Chouinard of Patagonia
Ian White, Director of Platform Engineering at DAT, joined the company to scale their Kubernetes-based cloud infrastructure, which has come under stress as their business has grown over the past couple years. Here he shares how he partnered with developers to learn about their challenges, how we conveyed a vision for how the company needed to evolve, and how he’s been working with development teams and business stakeholders to successfully drive change.
—
(01:00) - The challenges DAT was facing as Ian joined
(05:13) - How Ian used customer interviews to understand problems
(10:48) - The typical journey companies take as they scale their infrastructure as they grow
(16:20) - How early changes were positioned and received
(20:00) - The four personas Ian identified
(25:14) - How Ian evangelized the vision
(28:48) - Areas of pushback Ian foresees as they introduce new changes
(33:00) - Handling teams that want to stay on self-managed infrastructure instead of moving to a managed infrastructure
(41:55) - Managing business stakeholders
(45:00) - Partnering with finance
—
Where to find Ian:
Brian Guthrie, co-founder and CTO at Orgspace and former VP of Engineering at Meetup, has the unique experience of having previously decommissioned his Platform team. In this episode, Brian talks about that story openly, and shares advice for Platform teams to make sure they’re well positioned within their organizations.
Discussion points:
Follow Brian:
Mentions and links:
Max Kanat-Alexander and Or Michael Berlowitz (Berlo), share how they gather both periodic and real-time feedback from developers.
Discussion points:
Mark Côté, Director of Engineering of Developer Infrastructure at Shopify, explains an exercise the Infrastructure group went through to define their boundaries of work. He shares their areas of focus, the team’s guiding principles, how they use their developer happiness survey to decide what to prioritize, and more.
—
Discussion points:
(0:48) Mark's background
(1:43) How the Developer Acceleration org is structured
(4:43) The Infrastructure team's chart
(5:35) Three opportunities for impact
(7:49) Identifying the opportunities for impact
(10:51) Why they created a charter
(17:34) Infrastructure's guiding principles
(19:32) How they decide what to focus on
(21:44) Why they don't have product managers
(24:17) Ideas for reducing cognitive load
(29:05) Balancing customer requests with strategic roadmap items
(32:08) How Shopify's Developer Happiness survey works
(35:32) Who is involved in the Dev Happiness survey
(36:51) The survey's sampling strategy
(37:30) How the survey's results are used
(38:32) The survey's participation rate
(39:31) Steps they take after the survey
(42:52) Advice for others starting a developer acceleration team
—
Mentions and links:
Utsav Shah, who leads Platform at Vanta and previously led Developer Effectiveness at Dropbox, shares the story of Dropbox’s journey with measuring developer productivity. Utsav discusses what he learned about both system and survey-based measures, his opinion on the usefulness of common Git metrics, and more.
Michael Galloway (Doma and ex-Netflix) describes his process for interviewing developers to understand where his team should focus. He also explains how he thinks about the strategic value of a Platform team.
Resources mentioned:
In this episode, Willie Yao, Head of Infrastructure at Notion and former Head of Developer Infrastructure at Airbnb, provides a unique perspective on how Developer Experience teams work in hypergrowth companies. He shares how Airbnb developed a customer-first mindset internally, what it took to get Airbnb’s leadership invested in that effort, and how he’s approaching DevEx at Notion today.
Twitter’s Developer Experience team is more mature than most. Here, Jasmine James, a Senior Engineering Manager - Developer Experience, explains how her team manages support requests, why they consider personas as part of their prioritization, and how they present the ROI of the team’s work.
In this special episode, Dr. Nicole Forsgren, author of award-winning book Accelerate and co-author of "The SPACE of Developer Productivity", talks about her work with DORA, the inspiration behind the SPACE framework, and how she's thinking about developer experience.
Watch the on-demand fireside chat or read the announcement of Nicole joining DX as a strategic advisor.
Brent Strange, Director of Engineering Excellence at GoDaddy, has a unique perspective on the role of an internal enablement team because he focuses more on the people and processes instead of tooling. Here he shares his perspective on org structure, as well as the role of agile coaches and his response to some of the negative views that exist towards Agile.
Sylvestor George (Staff Software Engineer on Slack’s Internal Tools Team) led a project to move the entire development experience to remote environments, which was widely regarded as a “dramatically better experience”. Here he shares the full story of that project, including how they identified the problem, the solution they created, and how they convinced engineers to adopt the new workflow.
In this episode Abi Noda is joined by Crystal Hirschorn, who leads Platform Infrastructure, SRE, and Developer Experience at Snyk. In their conversation, Crystal shares the story behind the recently founded Developer experience group, including why they named the team Developer Experience, how she calculates the cost of the problems they solve, and how they partner with engineering teams.
Max Pugliese, formerly the Director of Developer Experience at IBM, offers a look at what it’s like to support tens of thousands of engineers. He explains why it’s important to think about the culture and processes surrounding the tooling changes a team tries to implement, how to stay close to developers, and more.
In this episode Abi speaks with Jelmer Borst, Product Manager for Picnic Technologies’ Platform group. Jelmer explains what the value is of having a PM in an internal-facing team, and shares his process for gathering feedback from developers to understand where they’re experiencing friction.
In this interview, Mojtaba Hosseini (Director of Engineering at Zapier) talks about how to approach using metrics, pitfalls teams run into, and the common evolution teams go through as they adopt metrics.
Julio Santana from Workday shares how he thinks about the ideal scope of a Developer Experience team, getting buy-in for DX initiatives, how his team gathers feedback from developers, and more.
In this episode we’re joined by Minh Pham and Titus Stone from Ibotta’s Developer Experience team. You’ll hear their story about how the DX team came into existence, why they view a DX team as a “startup within a startup”, and their vision for what DX at Ibotta will become.
In this episode Abi Noda speaks with Ryan Atkins, Asana’s Head of Engineering Operations. They talk about the role of EngOps and when it’s needed, founding an EngOps team, how these teams work in large companies, and more.
Will Larson, the CTO at Calm, covers a wide range of topics including whether Infrastructure Engineering is chronically understaffed, the role of Eng Ops, how his opinion on the “build vs buy” question has changed, his thoughts on metrics, and more.
Helpful resources:
Joining us for this episode is Victoria Morgan-Smith, the Director of Delivery for Engineering Enablement at the Financial Times. Victoria shares some of the tradeoffs in having an autonomous, “you build it, you run it” culture. She also shares how her group equips engineering teams with metrics, best practices, and more.
Follow Victoria on LinkedIn
In this episode Abi talks with Peter Seibel. Peter previously was the Director of Engineering for the Democratic National Committee, and before that led Twitter’s Engineering Effectiveness (EE) team. In this interview, Peter reflects on his experience at Twitter, sharing why it’s better to invest in EE early and his vision for how EE teams can fulfill their potential.
Useful links:
In this episode, Varun Achar (Director of Engineering at Razorpay) explains how the Platform org has grown from a 15-person team owning everything, to 3 separate subteams. He also shares how they think about creating a culture of productivity, and some of the tactics they’ve used for increasing service adoption.
Helpful links:
In this episode, Marco Chirico shares the strategies DoorDash’s Developer Productivity group uses to prioritize their work. He also explains how the Developer Productivity group has evolved over time, and how they measure their success today.
Useful links:
Liz Saling, Director of Engineering at GitHub, shares the story of how the Developer Experience group was founded and why GitHub paused features for a quarter to focus on making developer experience improvements.
Helpful links:
En liten tjänst av I'm With Friends. Finns även på engelska.