Who Built This Platform? Alternative Viewpoints on Platform Design - Diana Todea & Elif Samedin
summary
Platform design shows concrete fixes and results: teams replace Terraform/Ansible-as-docs with a single entry deploy flow and diagrams, add preview queries and restricted prod rights after a missing WHERE caused a full-table update, and swap opaque CI templates plus Kubernetes Carpenter defaults for RFCs and async reviews so app teams can troubleshoot. Metrics tracked include time to first successful deployment, self-service success rate, polling hit ~50 responses, and onboarding time measurably drops.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:45Underrepresented groups in platform engineering
- 6:16Platform design versus skill gaps
- 9:10Production incidents and human error
- 11:19Abstractions and tribal knowledge
- 14:29Who is the platform built for?
- 15:53Inclusive decision making for reliability
- 17:16Measuring developer experience
- 20:42Velocity versus continuous improvement
- 23:10Key takeaways
related talks
22mThe challenges of Platform teams
37mPlatform Engineering's Inferno
46mBeyond DevOps: How and Why Companies Converge on Platform Models
33mThe Platform Engineering Journey
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
35mPanel: Navigating the Path to Platform Engineering...
27mThe Future of Platform Engineering
44mIs Platform Engineering a hype? Let's build a platform together!