I'm not a huge fan of SOLID. It's treated as a pillar of software development, but I feel like some of the advice sounds good or is right but isn't terribly us

I'm not a huge fan of SOLID. It's treated as a pillar of software development, but I feel like some of the advice sounds good or is right but isn't terribly useful(SL), one was so terrible it was rebranded(O), and some are a useful tool more than a design goal(ID). Single responsibility principle - something we can all agree on but doesn't help you decide between two non hideous designs Open/Closed Principle - the original advice was so terrible that we ignore it and pretend it means something else that has very little to do with open/closed Liskov - technically true but very few applications are bad or incorrect because of this violation(especially with the recent move away from inheritance) Interface Segregation - Sure it's useful to split up interfaces sometimes. Dependency Injection - Sometimes useful for testing or IOC.