
Many people have responded on the quoted thread 👇 by saying there should be a "balance" between abstraction and no abstraction within a program. Somebody, please explain to me what that would look like. Maybe I have no imagination, but I envision a few classes floating around like meatballs in a sea of spaghetti. What would the architecture of such a system look like? How exactly will you get architectural coherence? How do you get maintainability in the spaghetti? These are all mysteries to me. How is that better than a system where everything is abstracted into classes? (BTW, I'm not talking about bad programming. Unnecessary interfaces are a scourge. Classes are not.) I'd like to see a concrete example.
Allen Holub. https://linkedIn.com/in/allenholub@allenholub
I really don't understand this entire thread 👇. We have a phrase for code without abstractions: unmaintainable spaghetti.
English



