https://news.ycombinator.com/item?id=34966137

🍿 Enjoying the screeching in the comments. :D

I would add: historically OOP movement did not make a good distinction between data and code. It's best when *data* is organized in a program like in a application-specific in-memory database (or just in a persistent database right away), while "objects" and interfaces are useful for *code*: https://dpc.pw/data-vs-code-aka-objects-oop-conflation-and-confusion

The biggest blunder in the Clean Code is the unconditional "prefer polymorphism over switch/if": https://dpc.pw/what-oop-gets-wrong-about-interfaces-and-polymorphism

Reply to this note

Please Login to reply.

Discussion

Can't agree more. But lots of schools/universities are still teaching the polluted idea of pre Java6 style OOP, which makes most new grad incapable of writing decent code and I have to retrain them at the job. A total waste of economic resource.