Closing panel: The future of platform engineering and what to build next
summary
Conference consensus names agentic chaos as the immediate problem and points to a real-world Fable 5 withdrawal event — a model that appears and is pulled within days — as proof that platforms must survive sudden dependency loss. Concrete recommendations: use infrastructure as code and optionality for alternate LLMs, build harnesses that route cheap models for simple tasks, enforce policy as code, set CPU/GPU limits, and design for non‑technical users (marketing, HR) who will spin up agents.
AI-written summary · about
chapters (7)
- 0:00Closing panel intro
- 1:58Today’s insights
- 6:33AI sovereignty and withdrawal
- 12:19AI agent costs vs governance
- 18:20Platform engineering beyond devs
- 23:19Building future-proof platforms
- 27:12Closing remarks
related talks
28mClosing panel: The future of platform engineering and what to build next
31mClosing panel: The future of platform engineering and what to build next
32mThe Past, the Present, and the Future of Platform Engineering
49mBeyond Engineering: The Future of Platforms
27mThe Future of Platform Engineering
46mPanel Discussion: The Agentic Software Factory That Enterprises Actually Need
37mPlatform Engineering's Inferno
35mPlatform Engineering Is Not About Tech