Spec-ulation Keynote
summary
Argues that spec is designed to enable safe accretion and detect compatibility using spec uses set logic for maps and regexes for sequences, not to forbid unknown keys; classifies change into require/provide directions (accretion, relaxation, fixation, fixing) and distinguishes levels (functions, namespaces, artifacts). Claims semantic versioning is broken because it collapses levels; praises Maven Central as an immutable, accreting registry; recommends adding new namespace/functions instead of breaking, using repo/sha-addressing and fine‑grain dependency testing to make upgrades safe and composable.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:58This is not a talk about spec
- 2:47'Change
- 7:42Dependencies Redux
- 10:46Dependency Truth (code)
- 13:46Do deps Force Versioning?
- 19:49(Ex)changes in Software • What is required?
- 22:12Growing Your Software
- 24:15Breaking Your Software
- 26:24Change is Not a Thing
- 27:56Recognizing Collections
- 29:53Semantic" Versioning "Semantics
- 33:07Which Name?
- 33:38Requiring More args? Providing Less on return?
- 40:33Doesn't Doing the Right Thing Name-wise Make You Reluctant to Remove Things?
- 41:02Breaking Changes are Broken
- 42:24So Maven is Broken?
- 48:47What about Git?
- 51:18Local dev vs Open dev
- 58:32What about Iterative Development?
