Want to build software that is more testable, modifiable, and has fewer lines of code? Architecting with immutable objects is the most important lesson I have learned in building better applications. Also, learn how to use immutable objects and collections to improve design of mutable entities.

Want to build software that is more testable, easier to modify, and has fewer lines of code? Architecting with more immutable objects that are always in a valid state is the most important lesson I have learned in building better software applications. Using immutable value objects will lead to less checking, fewer bugs, and more DRY code, and will help avoid the “spooky action at a distance” problem in PHP. We will also learn how to use immutable objects and immutable collections to improve design of our mutable entities. Lastly, we’ll see how immutable objects and functional programming can reduce complexity.

Comments

Please login to leave a comment

Philip Sharp at 14:44 on 2 Aug 2019

I came away understanding the core ideas. Some of the examples were hard to follow as they didn't always build on each other in order. I'd also like to see how to handle persistence with immutable entities.