Do high-level modules depend on abstractions rather than low-level details? This keeps components isolated and easier to test. 2. Reviewing the "Assume" Factor
Are interfaces small and specific? Clients shouldn't be forced to depend on methods they don't use. assume
If you are looking to review assumptions—whether in research, design, or personal life—a "solid" approach involves moving from guesswork to evidence. Do high-level modules depend on abstractions rather than
Does each class or module have only one job? For example, an email module should only handle sending emails, not deciding who gets them. Reviewing the "Assume" Factor Are interfaces small and
How to Stop assumptions ? Before you assume, try this ... - Facebook
When you hear "SOLID," you might be thinking of the gold standard for software design, or perhaps you're looking for a "solid" way to review the assumptions we make in everyday life. Since your request is a bit open-ended, 1. The Technical "SOLID" Review