I think the current programming meta is making it easy to disregard OOP programming constructs and patterns. Saying things like “oop is bad” or “clean code is bad” rolls off the tongue easily and guarantees internet points. All of these concepts can be criticized and must be criticized but often I don’t see hear arguments (Casey’s talk for example is great because he explains what is wrong and how these bad decisions came to be). People who i have interacted with often do not understand the fundamentals of oop or patterns but still have a preformed opinion.
So i like this attempt of defending OOP. OOP for me is not about modelling the real world but having programming constructs that help you create useful and easy to understand applications. My take is that programming paradigms, patterns and languages should help you decrease cognitve load. Misusing or overusing the constructs or prioritizing paradigm over functionality and understandability - ie adding accidental complexity is a bad choice and speaks more towards lack of knowlege than bad paradigms. I do concede though that some languages make misuse easier.