GO DEEPER ▸ Why we write Mutable code: ▸ We think in mutable constructs. ▸ In Java, final feels too verbose. ▸ Why immutable code is better: ▸ State. Have you turned it off and on again? ▸ Applies a limit, thereby forcing you to think.
IMMUTABLE, FUNCTIONAL CODE. REMOVING VAR’S LEADS TO REFACTORING. THE REFACTORING LEADS TO NEW CODING PATTERNS. NEW CODING PATTERNS LEADS TO A SHIFT IN YOUR APPROACH TO PROGRAMMING. THIS SHIFT IN APPROACH LEADS TO TRANSFORMATIVE CODE THAT HAS FEWER DEFECTS AND IS EASIER TO MAINTAIN. — BEGINNING SCALA, DAVID POLLACK
IMMUTABLE, FUNCTIONAL CODE. REMOVING VAR’S LEADS TO REFACTORING. THE REFACTORING LEADS TO NEW CODING PATTERNS. NEW CODING PATTERNS LEADS TO A SHIFT IN YOUR APPROACH TO PROGRAMMING. THIS SHIFT IN APPROACH LEADS TO TRANSFORMATIVE CODE THAT HAS FEWER DEFECTS AND IS EASIER TO MAINTAIN. — BEGINNING SCALA, DAVID POLLACK
IMMUTABLE, FUNCTIONAL CODE. REMOVING VAR’S LEADS TO REFACTORING. THE REFACTORING LEADS TO NEW CODING PATTERNS. NEW CODING PATTERNS LEADS TO A SHIFT IN YOUR APPROACH TO PROGRAMMING. THIS SHIFT IN APPROACH LEADS TO TRANSFORMATIVE CODE THAT HAS FEWER DEFECTS AND IS EASIER TO MAINTAIN. — BEGINNING SCALA, DAVID POLLACK