Closing keynote
summary
Argues a platform must enable uses its builders never imagined and contrasts toolkit vs framework tradeoffs using concrete examples: Kubernetes’ object model with metadata/spec/status and labels for predictability, KNative’s duck typing and conditions, and AWS’s inconsistent UX across services. Says Dapr mixes opinionated APIs for interservice calls with open-ended app internals; composes primitives so state + messages = outbox and state + invocation = actors. Urges layered defaults, targeted docs for depth vs breadth, and shipping early to get real user feedback.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:27Good developer platform
- 4:17Toolkits vs frameworks
- 7:04Predictability in platforms
- 10:13Layering complexity
- 13:42Documentation needs
- 15:29Platform builder curse
related talks
12mLightning Talk: Developer Advocate Plays Devil's Advocate: Platform Engineering Editi...
46mPlatforms: Build abstractions, not illusions
21mKeynote: Zen and the Art of Platform
41mPlatform Engineering for Developers, Architects & the Rest of Us
39mPlatform Engineering as a (Community) Service
10mSponsored Keynote: Crossplane - The Best Kept Secret in Platform Engineering
06mKeynote: PlatformOps: It’s all about Developer Experience
27mThe Future of Platform Engineering
