Some Principles From Real World Internal Developer Platform Engineering
summary
Practical principles for internal developer platforms: treat the platform as a habitat that lifts engineers up, use experiments with short feedback loops and leading indicators rather than big plans, instrument DX and measure behavior changes not vanity metrics, and optimize concrete UDA loops (observe → decide → act) to improve workflows. Concrete rules: aim for roughly 1:10 golden ratio of platform engineers to stream-aligned teams, preserve freedom to contribute and don’t feed the pigeons (don’t reinforce harmful workarounds), iterate until the ski-resort boundaries are clear.
AI-written summary · about
chapters (13)
- 0:00Intro
- 3:28My hope for this talk
- 5:4015 years ago
- 12:25Back to 2020
- 13:44A tale in 6 weeks
- 16:34Week 1
- 19:03Week 2
- 26:32Week 3
- 33:28Week 4
- 34:22Week 5
- 39:43Week 6
- 43:10Epilogue
- 47:30Outro
related talks
21mMake developers fly; Principles for platform engineering
23mPlatform Engineering for Architects - Crafting Platforms as a Product
29mImproving Developer Experience
16mPaved roads to hell: Antipatterns of platform engineering efforts
29mIaC Next Steps in Platform Engineering
23mPlatform engineering is all about product
39mThe challenges of Platform teams (and few tips & tricks...)
29mKeynote: Building Bridges with Platforms: The Role of the Platform Engineer