@grainloom i remember one of my intro classes to OOP the prof spoke for multiple classes about how it's the pinnacle of software. You can represent ANYTHING as an object! and INHERITANCE! and MULTIPLE INHERITANCE!
It was all described using the most elaborate marine terminology that I sure as fuck didn't understand because I wasn't rich with a yacht club membership, but he was so proud of his 6 hour long description of boats, club members, and their various shared attributes.
@adasauce @grainloom This sounds familiar to me and my university lecturers; they seemed so proud of this one domain they had modelled so well, but which was neither particularly illustrative nor useful, computationally.
@amdt @adasauce @grainloom I think that's a shortcoming with a lot of software engineering teaching, how it doesn't expose its value until you're working with something that's way too complicated to be an example in a class
I basically didn't get the value of a lot of OO stuff until I made a sufficiently-complex rails app six years after graduating university
@adasauce @grainloom you should make your friend watch the series of videos being OOP (YouTube, though). One of them is called "OOP is garbage" (sorry, cannot check direct links right now).