Scala bad practices or how to keep your job for life
summary
Argues that Scala becomes difficult when developers misuse its features rather than due to the language itself. Covers concrete problems: primitive obsession (using raw String/Int leading to subtle bugs), poorly wrapped Java libraries without proper adapters, mixing FP and OO patterns (mutable-to-immutable wrappers and turning sync calls into Futures backed by dedicated thread pools), and harmful implicit conversions—especially implicits placed in package objects that silently change types. Recommends fixes: introduce custom domain types instead of primitives, avoid implicits in package objects, and wrap external libraries behind clear adapters.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:32Primitive obsession
- 5:18Library-splaining
- 7:39Mixing paradigms
- 8:32DRY overuse
- 11:00Conciseness over readability
- 13:26Powerful Feature misuse
related talks
49mScala best practices I wish someone'd told me about
52mScala Best Practices I Wish Someone'd Told Me About
39mA few tips on modelling things in Scala
45mEffective Scala
52mImmaculate Code (pure code)
46mCode Smells - Hall of Fame
40mAssuring top-notch code quality in the Java Universe
23mDecoupling From (Bad) Shibboleths in the Software Developer Community