Buying into Scala from the Inside and Out
summary
Migration from a Perl monolith to a Scala microservice architecture produces five microservices and about 100k LOC within a year with a team that grows from two to eight developers; training combines a hired trainer two days/week with three days of hands‑on work, Scala microservice architecture, katas, coding dojos, pairing, mob refactoring and short workshops. Teams reach confidence in ~2 months but accept an initial productivity dip, favor early adoption of functional programming workshops and measure impact with defect and delivery metrics.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:15Meet Sofia and Dave
- 3:01Why Scala
- 6:37Learning
- 12:07Not equal to similarity
- 13:54Learning and teaching
- 17:23Peer review
- 21:38Pairing
- 26:59What you should learn
- 29:55Mistakes
- 35:22Language adoption
- 38:32Pitching Scala
- 41:33Metrics
related talks
23mOur 8 years journey with Scala
22mAdopting Scala: The Next Steps
51mDeus Ex Scala: Finding a Home for Scala in the Corporate Machine
38mMy first year in Scala
42mBuilding a Company on Scala
48mTeaching Scala A Roundtable Discussion
33mFrom Managing Scala to Managing People
44mTeaching Scala to the Statically Challenged