No, that wasn't your point. You were arguing that OOP leads to bad code and tried to prove so by providing one example of bad OOP code. But that doesn't show anything, you can make bad code in any paradigm or language. Especially if you set out to deliberately do so.

Effectively you're arguing "I don't know how to do OOP well, therefor it must be bad". Which is a very egocentric argument, either learn how to or just don't bother. But drawing the conclusion that it must be bad is just silly and ignores all the success other people have had using OOP, together with all the theoretic frameworks behind it.

I for one can't make any sense of how people make anything work in assembly, but I'm not going to rant on the internet about how stupid it is. Instead I just accept that there are things I know and things I don't know, and assembly firmly falls in the latter category.