I think php documentation mentioned some of these are for frameworks to change behavior of classes but isn't meant for normal use. It produces hard to understand and debug code, best practice was to try to avoid using them, ie the get and set functions. I've experimented with them for accessing database data and caching in memory like an orm but quickly changed my mind about because it was prone to errors, ide problems and other issues. On the surface it seemed like a good idea but digging deeper it's a complete mess.
![php[architect]](http://yt3.ggpht.com/17sMZ4iyRjqC_0z8qO5w-9AhAM1r_O9v_aGLvBcK5kykGsbV54jIrhXhjDf3EIbiMWp-ZkwckA=s48-c-k-c0x00ffffff-no-rj)
Thanks for this video. It was very informative.
Glad it was helpful!
Very good format for video series. Didn't know about some methods. Thanks
Glad you liked it and thanks for being a subscriber!
I think php documentation mentioned some of these are for frameworks to change behavior of classes but isn't meant for normal use. It produces hard to understand and debug code, best practice was to try to avoid using them, ie the get and set functions. I've experimented with them for accessing database data and caching in memory like an orm but quickly changed my mind about because it was prone to errors, ide problems and other issues. On the surface it seemed like a good idea but digging deeper it's a complete mess.