LIQUID code principles as opposed to SOLID
Today I want to talk about bad practices!
And a great way that me and a great friend
Came up with, to remember them by
There is the famous SOLID acronym
Which specifies a set of neat architecture practices that could be
A great tool in your arsenal for designing clean and easier to maintain
So let’s talk about bad practices!
Kind of the opposites of the principles mentioned above.
The opposite of SOLID is of course LIQUID!
Large! large modules, files, functions, classes
Imperative code, numerous statements that manipulates state
In order to acquire the application’s goals.
Often most of the code we read and write, consists of implementation
Details and almost nothing is encapsulated and declarative.
Unclear variables names, complex, nested statements
And functions, lots of unclear and outdated comments.
Small amount of modules and functions, that are doing most of the heavy lifting, Everything in one place, no design principle is taken into account.
Lots of unnecessary code
Lots of unnecessary operations
Synchronized when possible
Use lots of bad practices, old libraries, frameworks, languages,
And APIs that are nearing their end of life.
Sounds familiar?? :)))