Assume

How to Stop assumptions ? Before you assume, try this ... - Facebook

Can a subclass replace its parent class without breaking the program? If is a subtype of , you should be able to use is expected.

Are interfaces small and specific? Clients shouldn't be forced to depend on methods they don't use.

If you are looking to review assumptions—whether in research, design, or personal life—a "solid" approach involves moving from guesswork to evidence.

Can you add new features without changing the existing source code? Entities should be open for extension but closed for modification.

Does each class or module have only one job? For example, an email module should only handle sending emails, not deciding who gets them.

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

In software engineering, a refers to checking code against five key principles to ensure it is maintainable and scalable.