> In what job you don't need to worry about what code are you executing? Worry about? Or understand the fine minutia of how every property you fetch or store i

> In what job you don't need to worry about what code are you executing? Worry about? Or understand the fine minutia of how every property you fetch or store is handled? > It makes my job much harder to do, much more hidden and arcane I don't know how you do your job, but seeing a real (i.e. not a faux property handled by __get/__set) class member's implementation is literally 1 click away in any decent IDE. Clicking to see the potential hooks of a field vs clicking to see the getter or setter (which may or may not even be defined in the same class) is no different. > Yes, reflection is a mistake. It's a hotfix for problems caused by OOP. It's not actually necessary. Right. I guess that's why it's applicable to functional programming. To be a hotfix for OOP? https://www-master.ufr-info-p6.jussieu.fr/2007/Ajouts/Master_esj20_2007_2008/IMG/pdf/malenfant-ijcai95.pdf https://www-master.ufr-info-p6.jussieu.fr/2007/Ajouts/Master...