Developer Platforms People Actually Adopt: Lessons From Three Failures
Sofia Lindqvist
- When
- Tuesday, September 151:15 PM – 1:45 PM · 30 min
- Where
- Room 2BFort Mason Center, San Francisco
About this session
We built three internal platforms nobody used before one that stuck. The difference was never features — it was migration cost, escape hatches, and letting teams keep their own deploy buttons.
Speaker
Engineering Manager, Norrsken Data
Sofia manages the developer-experience group at Norrsken, a team she started by asking every engineer which internal tool they would delete first. She has been an SRE, a compiler engineer and, briefly, a professional oboist.
More in Developer Experience
- From Notebook to Service in One AfternoonTime to be announced
- Streaming Structured Output: UX Patterns Beyond the Token FirehoseTuesday, September 15 · 10:30 AM – 11:00 AM · Room 2B
- Design Systems for AI Products: Calm Interfaces for Chaotic ModelsTuesday, September 15 · 11:15 AM – 11:45 AM · Room 2B
- Undo Is a Feature: Designing Reversibility Into AI ProductsWednesday, September 16 · 11:15 AM – 11:45 AM · Room 2B
- Growing an Engineering Org Around an AI ProductWednesday, September 16 · 1:15 PM – 1:45 PM · Main Stage
For developers: this programme is open data — JSON, iCal, schedule XML and an MCP endpoint.Show endpointsHide
- JSONEvery published session and speaker, in one request./ai-builders-summit-2026/feed.json
- iCalSubscribe in Google, Apple or Outlook Calendar./ai-builders-summit-2026/feed.ics
- Schedule XMLfrab / pentabarf — the format conference apps import./ai-builders-summit-2026/feed.xml
- MCP + RESTPoint Claude at the programme. OpenAPI 3.1 included./agents
No key, no signup, CORS open. Everything here is generated from the same data the organisers edit.