"KISS" is another popular Design Principle in Software Engineering.
Here's what it means in 6 simple steps:
Here's what it means in 6 simple steps:
1. KISS Stands for "Keep It Simple Stupid"
2. It says prefer simplicity over complexity.
Systems should be designed by keeping simplicity in mind, if it's not required don't add any unnecessary complexity to your design.
Systems should be designed by keeping simplicity in mind, if it's not required don't add any unnecessary complexity to your design.
3. Simple code is easy to understand, and maintain.
It leaves a very small chance for any bugs and is easy to debug.
Requires less time to write the code.
It leaves a very small chance for any bugs and is easy to debug.
Requires less time to write the code.
4. Consider the below design where you want Reach A to B state.
In 1st, we overcomplicated the design which makes it hard to keep track of our system flow & difficult to maintain.
In 2nd, we've got a simple design easy to understand, & maintain. This is KISS Principle.
In 1st, we overcomplicated the design which makes it hard to keep track of our system flow & difficult to maintain.
In 2nd, we've got a simple design easy to understand, & maintain. This is KISS Principle.
5. When to apply KISS?
The idea is to design a system simple, if you are using some fancy feature from some library and only using it for sake of best practice don't do it because it's complicating the design.
Overoptimization of code also sometimes leads to complexity.
The idea is to design a system simple, if you are using some fancy feature from some library and only using it for sake of best practice don't do it because it's complicating the design.
Overoptimization of code also sometimes leads to complexity.
Always remember Less is More.
Don't use a design pattern for sake of using it if it's not solving a bigger problem.
Before writing code, think twice about how can we make it more simple.
Don't use a design pattern for sake of using it if it's not solving a bigger problem.
Before writing code, think twice about how can we make it more simple.
6. When not to apply KISS?
Don't comprise your system security by running behind simplicity. Security should be a top priority.
Don't simplify if your code is exposed for unwanted modification (Remember Open-Closed Principle from SOLID).
Don't comprise your system security by running behind simplicity. Security should be a top priority.
Don't simplify if your code is exposed for unwanted modification (Remember Open-Closed Principle from SOLID).
That's a wrap!
I help people get started with Backend Development.
Follow me @vikasrajputin for more.
If you find this thread helpful then Like/Retweet the first tweet below:
I help people get started with Backend Development.
Follow me @vikasrajputin for more.
If you find this thread helpful then Like/Retweet the first tweet below:
Before you go, do you know?
I also write on LinkedIn!
I share some exclusive content there, which I never share here.
Follow me on Linkedin to never miss an important update on Backend content:
linkedin.com
I also write on LinkedIn!
I share some exclusive content there, which I never share here.
Follow me on Linkedin to never miss an important update on Backend content:
linkedin.com
Loading suggestions...