DX for Internal Teams
summary
Company runs ~100 developers, 5-person DX team and shows concrete wins: a custom neo cli and neobot (Slack bot) that pull multi-repo code, deploy branches to integration, and surface owners; several web apps (build monitor, coverage collector, transaction simulator); custom GitHub Actions for PR ticket checks and GraphQL breaking-change checks; metrics flow to Datadog tracking command usage and help-text errors to prioritize fixes; claim: saving minutes per dev scales like hiring another engineer.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:46Examples of Good DX
- 2:17Neo
- 3:07Developer Flow
- 4:14Hiring is Hard
- 5:06When should you start?
- 5:41It's Never Too Early!
- 6:10Turn That Collection of Scripts Into a CLI
- 6:23Turn Those Notes Into a Wiki
- 6:49Working Locally
- 7:08Continuous Integration and Deployment
- 7:25Code Quality and consistency
- 7:47Security and Compliance
- 8:04Onboarding
- 8:30Custom Tools
- 10:57Resources
- 12:13Developer Relations
- 13:42Don't Do It Alone
- 14:20Treat Tools Like Production Software
- 14:42Metrics and Analytics
- 15:43Error Reporting and Logging
- 16:05Solicit Feedback
- 16:41Publicize New Features
- 17:09Documentation
- 17:31Automatic Updates
- 18:12Make Tools Fun!
- 18:52DX for Internal Teams
related talks
42mBuilding DevX Teams, my story
31mDX to another level
25mUX, DX, DSX: Developers and Data Scientists as Users
20mEmpowering Developers: Driving Innovation for the Future of Work TechLead
34mFrom Developer Experience to Business Value
50mDevEx on Steroids: 5 Techniques to Scale Developer Experience
53mLet's talk about DX, Baby!
29mDX is UX