~/talk

Socio-technical API patterns

Talkat NDC Oslo 2026 · 2026-09-14..09-18· [api-design, software-architecture]
links:none on file
slides:none on file

Argument: APIs fail or succeed as socio-technical systems, not just code. Shows recurring patterns — Millstone (reluctant internal provider exposes raw data, creating long-term coupling), Rapids with Beaver Dams (API sits mid‑value‑stream, teams drift, consumers build fragile workarounds), and escalation to OpenAPI contract vs reverse‑engineered docs. Recommends bilateral co‑authored contracts, SLAs, API keys, anti‑corruption layers and team merges; notes unilateral design is still the most common practice and usually causes the problems described.

AI-written summary · about

  1. 0:00Introduction to APIs
  2. 3:20Social-technical systems matter
  3. 14:11API design process realities
  4. 27:13Millstone pattern explained
  5. 32:07Mountain and volcano patterns
  6. 35:00Rapids and sock puppet patterns
  7. 41:14Leech and covert consumers
  8. 45:27Endless possibilities anti-pattern
  9. 48:33Crowdsourcing API patterns
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.