Guys I need some helping hand. I need some good reading (book/article) on the proper way of writing OOP. I gave a project where we use classes, but they are more used as a package if functions then working like objects. Like a class of only statics, passing around IDs not the real objects of data (this sending SRP down the drain), arrays, generally functional programming with extra steps. I'd fancy even a discussion as I want to slowly explain all that to my teammates #php#oop#programming
TIA
@djumaka I find thinking in types is what is more valuable. Don't think of an object as behavior, but a custom type. A primitive in your domain. Now attach a few contextually relevant utilities to it.
Really I think about OOP very functionally these days. :-)
(What you're describing is procedural, not functional.)
Add comment