Ship It! Cloud, SRE, Platform Engineering Developer Experience Infrastructure (DXI)
In your company, who designs the end-to-end developer experience? From design to implementation, what is the developer experience that you actually ship? Even though the average developer wastes almost half of their working hours because of bad DX, many of us don’t even know what that means, or how to improve it.
Kenneth Auchenberg is working at Stripe, building economic infrastructure for the internet. Gerhard found his perspective on Developer Experience Infrastructure (DXI) refreshingly simple, as well as very useful.
Changelog++ members save 2 minutes on this episode because they made the ads disappear. Join today!
Sponsors:
- FireHydrant – The reliability platform for every developer. Incidents impact everyone, not just SREs. FireHydrant gives teams the tools to maintain service catalogs, respond to incidents, communicate through status pages, and learn with retrospectives. Small teams up to 10 people can get started for free with all FireHydrant features included. No credit card required to sign up. Learn more at firehydrant.com/
- Sentry – Working code means happy customers. That’s exactly why teams choose Sentry. From error tracking to performance monitoring, Sentry helps teams see what actually matters, resolve problems quicker, and learn continuously about their applications - from the frontend to the backend. Use the code
CHANGELOGand get the team plan free for three months.
Featuring:
Show Notes:
- The tweet that started this episode
- 📝 Developer Experience Infrastructure (DXI)
- The Radiating Circles of DX Architecture - How to design an end to end developer journey - Shawn “swyx” Wang
Developer Experience is the new hot thing, and we now see many existing teams re-labeled as Dev Experience. What does DX really mean, and what is the relationship between developer relations, advocacy, DX, and product teams?
@auchenberg Twitter 🧵
Something missing or broken? PRs welcome!