Uploaded December 2020 | Updated September 2026, 1 week ago
In object oriented programming, we're taught to build "smart" classes. These are classes that have state and behavior such that an order object can save/delete/retrieve etc, In this video I make a case for why class that have state should not have behavior (and should be immutable) and classes that have behavior should not have state.
The Entire solution for the code shown in this video can be found here:
github.com/matlus/MovieServiceYouTube
In object oriented programming, we're taught to build "smart" classes. These are classes that have state and behavior such that an order object can save/delete/retrieve etc, In this video I make a case for why class that have state should not have behavior (and should be immutable) and classes that have behavior should not have state.
The Entire solution for the code shown in this video can be found here:
github.com/matlus/MovieServiceYouTube
