My god.
A lot of these fancy language features sound good on paper but can be so abused that even just coming to understand the code takes up too much space in your head.
Also gofmt having the last word on what code is acceptable and what isn't helps kill a lot of arguments that aren't worth having.
https://www.youtube.com/watch?v=rFejpH_tAHM is a good overview.
It is - in execution (message passing), not in taxonomies. You can't model the taxonomies because all set-in-stone languages are inadequate for that (see SICP, for example). Also, it sounds like someone had an inheritance mania on your project. That's an instant loss right there. (But maybe the language used didn't allow for anything better? C++ is notoriously bad in this respect, for example.)
That is definitely the way I was taught OOP in college. I came out thinking it as a steaming, overcomplicated pile of shit. I have since learned better. Of course, there is a whole world of enterprise programmers for whom what was described is "proper" OOP.
It is what I had to deal with, though.
These languages, as well as things like WSDL/SOAP, are the late 90's/early 00's snake oil designed to woo clueless manager-types into funneling money to consultants and 'architects'.
I worked a lot with those types and saw the futility of suggesting 'simple' solutions to simple problems - everything had to be over-complicated to justify their salaries.
It left me pretty bitter towards that whole business model. Then again, there's lots of money to be made there....
interface -> abstract -> base -> TheOnlyImplementationInstantiated
Repeat for a couple more chains, and one line bug fixes require visiting a dozen files to figure out.
* abstract class Connection would have maybe 3 or 4 methods;
* DataConnection would extend Connection and add a couple more methods that were specific to some proprietary protocol.
* POSDataConnection would extend DataConnection and wrap this proprietary protocol for POS machines
* ControllerDataConnection would extend POSDataConnection because a Point of Sale controller is technically a POS machine with a bit more functionality (Really just a couple flags turned on).
* There was plenty more in between; it's been so long now that I've forgotten it all.
It's just like we all learned in college! Object Oriented programming is supposed to model real-life! Except no, it's not. That's stupid and complicated.
Now the part of the OS that was C/C++ was absolutely beautiful. It took the UNIX style of programming / applications seriously; every little piece was its own program, and it worked flawlessly. Anyone could jump in and get to work immediately because it was so well written. You could follow any program top to bottom and it just... made sense!