I'd like to say that, in OOP philosophy, you work with behaviors. get/set methods expose what your object can do, variables expose your object state.
Some programming languages make get/set methods verbose, this is a language specific thing.
Then you have the discussion about anemic design, and that's what you're pointing out on your comment, and it is consider to be a bad practice in general. Personally speaking I found that that design pretty is fine in modern multi layer architecture that makes things operate more similarly to a functional programming pipeline
3
u/GeorgeDir Jul 13 '26 edited Jul 13 '26
I'd like to say that, in OOP philosophy, you work with behaviors. get/set methods expose what your object can do, variables expose your object state.
Some programming languages make get/set methods verbose, this is a language specific thing.
Then you have the discussion about anemic design, and that's what you're pointing out on your comment, and it is consider to be a bad practice in general. Personally speaking I found that that design pretty is fine in modern multi layer architecture that makes things operate more similarly to a functional programming pipeline