I want to introduce my own: KOST, which stands for KISS Or SOLID Tradeoff. KISS leverages the ability to make assumptions about the usecase. SOLID aims to remove any such assumptions as we can’t quarantee they hold in future. As we can’t leverage assumptions we removed, or remove assumptions we leveraged, the principles are inherently contradictory. You can’t use them both, at least inside the same scope. Any attempt of such will necessarily violate one or both. You could design the interface with SOLID and implement it with KISS. This means you make every assumption the interface allows, meaning all advantages of SOLID are lost below this level. On the other hand, not making assumptions above this level likely made your code much more complex than your current needs would require. KOST stands to remind you of the real strength of KISS. It’s the ability to make assumptions. Not worrying about the future is the stupid part, and it is the key for reaching simplicity. If the part of your brain considering SOLID principles isn’t screaming in pain, your code violates KISS. You are being smart by thinking ahead, and for that you must pay through complexity.
These videos would be great if they weren't rushed through. People only get hyped over the animations like they're watching a Saturday morning cartoon. 🤣🤣
Speak for yourself.. you are waiting to be spoonfed rather than taking what you learn from here and expanding on the knowledge. The videos are clearly not for beginners
These videos are supposed to be refreshers. I love the short format with simple examples. It gives me a quick overview of concepts that I haven’t seen or used in a while.
I want to introduce my own: KOST, which stands for KISS Or SOLID Tradeoff.
KISS leverages the ability to make assumptions about the usecase. SOLID aims to remove any such assumptions as we can’t quarantee they hold in future.
As we can’t leverage assumptions we removed, or remove assumptions we leveraged, the principles are inherently contradictory. You can’t use them both, at least inside the same scope. Any attempt of such will necessarily violate one or both.
You could design the interface with SOLID and implement it with KISS. This means you make every assumption the interface allows, meaning all advantages of SOLID are lost below this level. On the other hand, not making assumptions above this level likely made your code much more complex than your current needs would require.
KOST stands to remind you of the real strength of KISS. It’s the ability to make assumptions. Not worrying about the future is the stupid part, and it is the key for reaching simplicity.
If the part of your brain considering SOLID principles isn’t screaming in pain, your code violates KISS. You are being smart by thinking ahead, and for that you must pay through complexity.
That sounds interesting, thanks
KISS - Keep it small and simple.
Thank you always sahn lam
A good example of PACELC might be useful, but great summary and animations, and loved the KOST below :P
Also 2:35 maybe you meant "NoSQL" ( not NoQSL )
Thank you for doing this.
I love your videos alot
Hello, what tools did you use to make this video?
following
Read description.
Great
Great thanks
Hi 🖐🖐
As Always, The Best. 🔥
AMAZING
These videos would be great if they weren't rushed through. People only get hyped over the animations like they're watching a Saturday morning cartoon. 🤣🤣
Speak for yourself.. you are waiting to be spoonfed rather than taking what you learn from here and expanding on the knowledge. The videos are clearly not for beginners
These videos are supposed to be refreshers. I love the short format with simple examples. It gives me a quick overview of concepts that I haven’t seen or used in a while.
I always think about KISS when I develop
I always think about KISS at night
control man control 😂@@TomNook.
The robot rebellion will begin when the robots get fed up with humans forcing them to eat.
my favourite is ihp, that is I hate programming
Poor ostrich
FFS