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, more DRY code, and 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 are closed.

Hugo Hamon at 12:37 on 27 Jan 2018

Brilliant talk! Nicely presented, great real world examples, very useful. It’s hard to imagine there are so much to say about immutability in OOP unless we attend your talk. Thank you very much again. Hope to see your slidedeck publish somewhere.

Martin V at 13:04 on 27 Jan 2018

Really good presentation and nice speaker skills, well done! Some brewery calculations were not very interesting, to be honest, but I believe you had to introduce them to make your examples more "real world" ;)

Tim Mourik at 13:33 on 27 Jan 2018

Great talk, good realistics examples. Thumbs up!

Good talk, good examples. Learned something.

(Didn't like the topic of the Beer, but that is personal preference so I'm not going to let that affect my rating.)

Stef Liekens at 20:47 on 27 Jan 2018

Nice presentation with good tips.

The brewery formules were maybe too difficult to understand quickly ;-). However the many code examples gave me a good insight in immutability and DDD.

Ike Devolder at 11:06 on 28 Jan 2018

Great talk with a nice story. Great examples of what can go wrong when you are not using immutability

Guy Steels at 12:47 on 28 Jan 2018

Great talk. Very good speaker. We all love beer.

Jasper Kennis at 14:46 on 29 Jan 2018

Very convincing and practical. Also, beer.

Timo Schinkel at 15:46 on 29 Jan 2018

I liked the parallel with the brewing process that was made throughout the talk. This really helped making the example understandable. Would have liked to see more on the edge cases; when would and when wouldn't we need to use immutable objects.

Pim Elshoff at 21:48 on 29 Jan 2018

Excellent, in-depth, quality content and a very solid speaker. Two things I think could be improved is the structure and the closing. You suggest a structure consisting of four parts and you show which part we're currently at but then jump back and forth. That's a little bit confusing and I'd prefer a linear approach. As for the closing, you add a few more points at the end to send the attendee away with, but imho that's too much and I'd prefer you to save some content, such as the part on FP, for your follow-up talk that I very much would like to see from you.

Maybe too much brewing details

Anonymous at 09:18 on 30 Jan 2018

Great talk and speaker! This was one of the talks I felt compelled to start doing more of directly. Thanks!