The team is the least centrally focused, which I mean to say, we aren't all doing one task together and then getting that done. The part that hurts or the trade off that we get from being on the platform side is not being as well attached to the product engineering side. We're a little detached from them and we have to work extra hard to make sure that we're actually engaging with them to figure out what their problems are so that we can go and solve them. It was causing us a ton of problems because everything was a big tangle of code, and we're turning that into many repos. Local development for serverless is kind of difficult to do local development for
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