Comments by "p11" (@porky1118) on "Reacting to Controversial Opinions of Software Engineers" video.

I don't agree, Unity does OOP right. They have triple or more inheritance for a simple example camera implementation. And every class overrides some methods of the parent class. It's easier to write your own camera controller than trying to understand that one...
1
What I don't like about OOP: Overriding methods. Especially if you override them over and over again. Mostly you should have abstract methods. In this case you should use abstract classes, interfaces, traits or however they are called in your language. Your abstract methods might have default definitions, which can be overridden exactly once. There should be tools to enforce this, preferably by default. I like how Rust handles this using traits. But most of the time, I have to use inheritance or define some fields, which I only use in specific cases, when I use some OOP language, where I would use enums in languages like Rust, which seem much better suited for that use case. What I also don't like about common OOP languages: You are not allowed to define functions outside of classes. You have to create classes with static methods or something like that. But that's not a problem of OOP itself.
1
6:28 I would probably be a good teacher. If an intern doesn't know how to do something, I don't offer the "right way", but tell them a few options I have in mind, which could work, and also often ask, if they have a better idea. Or if I look at code other people wrote, I often say, what they could have done better and why I think, this is better that way, but as long as it works and I don't have to work with it, I don't force anything.
1
I agree about the last point, that you should write the readable stuff first. I would expect the compiler to be smart enough to make it efficient. If not, it's a bad compiler. In your example case, the compiler even has more information. It knows, the method is called for every element once.
1