Making Sotware Better, Despite Having Users
summary
Argues tradeoffs with concrete examples: ScalaTest sees half a million downloads so changes matter; a compiler plugin catches triple-equals misuse (avoids runtime test failures); a position macro leaked full file paths breaking reproducible builds and gets fixed by an env‑flag then an Option in the next major release. Explains versioning promises, 18‑month deprecation windows, and the need for automated migration tools and small hops toward Dotty. Useful if judging whether proposed fixes, migration strategy and real failures matter to your codebase.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:58Why Scala
- 7:43Users
- 12:15Benefit vs Cost
- 18:30Version Numbers
- 25:10Keep Your Promise
- 25:22Deprecation
- 26:28Silent killers
- 28:03Migration tools
related talks
29mAging: Evolving Software, Tools, and Ourselves.
46mThoughtful Software Engineering
16mBetter Stories, Better Software
01h 21mTradeoffs in the Software Workflow
01h 06mDecisions, Decisions — Dan North on Trade-offs in Software
56mThe art of keeping your project from falling apart
44mLies we tell ourselves about developer infrastructure
54mKeynote – Kent Beck