Programming principles: SOLID vs. FLUID

As Mr. Kralj puts it:

Everybody talks about S.O.L.I.D.

But no one mentions the opposite principles

Well said!

Classic principle is defined as:

• Single Responsibility
• Open-Close (this one is hard to grasp!)
• Liskov Substitution (this one is even harder!)
• Interface Segregation
• Dependency Inversion

This new(er) priciple defines opposite for crappy code:

• Fragile
• Lax
• Untested
• Insecure
• Disorganized

Alternate F.L.U.I.D. clarifies original S.O.LI.D. and is from 2011:

• Functional
• Loose
• Unit Testable
• Introspective
• (i)Dempotent

However, I found Mr. Henney's concept of re-doing S.O.L.I.D. with clarifications and went with Mr. Kralj's derivative of defining the opposite instead.

Credits to Mr. Harjot Singh for his original artwork at https://harjotse.medium.com/solid-principles-df26a1b131cb and Kristian Kralj for his idea!