Closing Panel
summary
Documentation is the most basic part of a platform and often the first fix; teams start by putting a ticket-to-portal workflow on top of existing processes before automating. Examples mention Terraform/CDK-level detail, Kubernetes for containers, Renovate for day‑two dependency updates and Port as a demoed IDP. Expect more abstraction, automation and AI to handle day‑two ops. Survey figures cited: 85%/40%/50% survey (devops practices vs platform awareness vs reported benefits).
AI-written summary · about
chapters (14)
- 0:00Closing panel welcome
- 1:10Day's lessons and surprises
- 2:34DevOps vs platform engineering
- 4:00Supporting developers with platforms
- 6:47Good developer experiences
- 8:11Future of platform engineering
- 12:47Developer portals challenges
- 15:21Abstraction vs organizational structure
- 17:44Resistance to platform change
- 19:32Overcoming resistance to change
- 23:01Communicating platform ROI
- 25:09Amplifying platform impact
- 26:55Empathy in platform communication
- 29:00Final takeaways
related talks
38mPlatform Engineering in the Age of AI Teammates
31mClosing panel: The future of platform engineering and what to build next
30mAutomate All the Things Panel Discussion
44mBeyond Metrics: Orchestrating Developer Delight with AI driven Platform Engineering
28mClosing panel: The future of platform engineering and what to build next
26mArchitecting Agentic Development Platforms
19mWrap: What To Build Next
23mPlatform Engineering Untold Truths