The Pipeline Is Dead

on YouTube ↗20m

" summary

Claim: the one-version pipeline is obsolete because code can be produced at runtime and personalized for each user. Built prototypes at Differ that deploy a stem plus immutable divergences so each session runs an isolated variant; examples include CRM personalization where fields and flows adapt and can roll back. Key mechanics are inspectable attributable and reversible divergence provenance, testing at scale, and coordination via merge intent not code. Hard problems remain; work is ongoing, not finished.

AI-written summary · about

" chapters (11)

1. 0:00Frozen artifact assumption
2. 1:45Pipelines as default
3. 3:53Cost collapse per-user software
4. 5:17Personalized software demand
5. 7:48One stem many divergences
6. 8:31Brittleness concerns
7. 11:24Adaptive software CRM example
8. 13:13Adaptive software challenges
9. 16:26Autonomy versus control
10. 17:51Beyond code generation
11. 18:55Adaptive software inevitable

" related talks

• 34mBeyond Continuous DeliveryChris Hilton · Jenkins User Conference San Francisco 2014
• 44mThe Pipeline Driven Organization｜Roy Osherove · Øredev 2019
• 41mThe Pipeline-Driven OrganizationRoy Osherove · GOTO Amsterdam 2022
• 34mBeyond Continuous DeliveryChris Hilton · Jenkins User Conference US West (JUC San Francisco) 2014
• 21mDesigning Modular Data PipelineKrzysztof Zabłocki · try! Swift Tokyo 2025
• 36mDeveloper Experience Trends & PredictionsJames Governor, Jyoti Bansal · Developer Experience Summit 2025
• 40mDeclarative Pipeline 2019 - Tips, Tricks, and What's NextLiam Newman · DevOps World | Jenkins World 2019 San Francisco
• 44mQA in a Pipeline Based OrganizationRoy Osherove · HUSTEF 2019