> This was a revelation to me and got me thinking: what is OOP actually trying to solve? This is the problem in a nutshell. Someone comes up with sensible ad

> This was a revelation to me and got me thinking: what is OOP actually trying to solve? This is the problem in a nutshell. Someone comes up with sensible advice, and like a bad game of telephone it gets stripped down to some brain-dead phrase that gets parroted around by reflex. And it's everywhere in software. It was always things like "prefer composition over inheritance when possible" - people chose to ignore it, and go ham with sprawling inheritance trees and design patterns for different languages because of a superficial understanding of software because we optimize for all the wrong things. There's interview questions where they'll ask what are the four pillars of oop or some nonesense, and one of them will be inheritance or something and so if you're not doing it that way, it's bad practice.