dpc on Nostr: https://news.ycombinator.com/item?id=34966137 🍿 Enjoying the screeching in the ...
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
🍿 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