Building Safe, More Testable Scala Production Systems
summary
x.ai describes concrete fixes: a triple equals type-safe equality operator, type wrappers for IDs (value-class optimization), and a custom safe string/contains API to stop common bugs that once sent ~300 spam emails. Tooling uses ammonite for live debugging, stores JSON snapshots and replay to run regressions, and compares outputs across branches. The decision service separates IO from pure logic, enabling thousands of fast, concise tests over a 100k‑line codebase and automated diff reports on every PR.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:34Agenda
- 13:57When To Use Type Wrappers
- 17:51How Do We Deploy Safely
- 18:46What Does It Mean To Be Testable
- 36:24Separation of I / O and Business Logic
- 37:17Contact Details
- 39:29Performance Impact
related talks
32mMaking software better despite having users
31mScala Quality assurance
32mMaking Sotware Better, Despite Having Users
19mExploring Scala Tooling ecosystem
29mExploring Scala Tooling ecosystem
42mHow We Built Tools That Scale to Millions of Lines of Code
49mScala best practices I wish someone'd told me about
46mThoughtful Software Engineering