Object-Oriented C++ - Dependency Inversion Principle

D dependency inversion principle is that you want high level things depending on other high level things, not low level things. Interface segregation only useful in very specific situations and I don't really find myself in those situations anymore. Solid principles are like, they start off real strong, you know, yes, single responsibility yet totally get that. Open close principal makes total sense. List got substitution may have been a prank.