Skip to main content

MOULD–the opposite of SOLID

·79 words·1 min

The engineering team at Blinq were considering what the opposite of SOLID would be, and we came up with the following:

  1. Multi-responsibility — classes can change whenever & whatever they want
  2. Open-Open — everything should be extendible
  3. Un-Liskov substitution principle — functions that use pointers should clone those values for themselves.
  4. Lower-level Interface Dependency Principle — all classes should depend on some sort of lower-level interface.
  5. Dependency-Dependency Principle — rely entirely on a third-party API instead of using abstractions.