Effective Scala
summary
Argues Scala works best as a third way — pragmatic functional object‑oriented code — and gives three concrete rules: pick a project opinion and stick to it, prefer val pointing to immutable data (the immutability matrix), and confine mutation to tiny hotspots. Shows real code: List.exists and mkString use internal vars or StringBuilder for speed yet remain pure externally; demonstrates PDF generation using the Java iText library inside a confined I/O region; plans ~50 guidelines in a book.
AI-written summary · about
