Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Classes, Inheritance, and Interfaces

Name: Anonymous 2018-10-30 22:09

I learned about classes, inheritance, polymorphism, and interfaces in my CS classes. We ended up doing assignments where everything was a user-defined class, and we made subclasses and we were obsessed with constructors and destructors and getter and setter functions (bad antipatterns basically), as well as unnecessary access modifiers. Everything was based around the idea of extensibility, and how future people would be forking our code and adding additional features.

But it all seemed so unnecessary. My real programs end up having 1-2 classes tops. A lot of OOP seems unnecessarily hierarchical.

What's the point in turning everything into a class? Not everything is going to be reused endlessly. A lot of it seems like ENTERPRISE QUALITY busywork to fill 40 hours a week with what seems like work.
https://en.wikipedia.org/wiki/Parkinson%27s_law
work expands so as to fill the time available for its completion

Name: Anonymous 2018-10-31 14:19

C++ is not fixated on anything, it's a fucking mess. they throw anything they can in there.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List