“Make everything as simple as possible, but not simpler” -Albert Einstein (paraphrased) And when you’re in the military, it’s incredibly important to send and process information quickly and without ambiguity. Unnecessary complexity gets in the way of purpose and should be avoided at all times. The idea behind it is that most processes or systems work best if they’re kept simple. Clarence Leonard (Kelly) JoHnson - A Biographical Memoir by Ben r.There’s a saying the US Navy coined in the ’60s: “Keep It Simple, Stupid” - or KISS for short.Keep It Simple Stupid Principle (KISS Principle).KISS (Keep it Simple, Stupid) - A Design Principle.Doing so gives you actionable things to do. However, with these things (Like business strategy), you can split your solution into simple steps. Sometimes, keeping the big picture is vital, or splitting is not possible. There are some tasks that you can not solve only through KISS recursion (split-solve cycle) alone. Simple as the final answer to everything, without thinking.Simple solutions are not bad or lacking to solve complex issues (you should not have a complex issue in the first place, split it!) To quote Einstein: Everything should be as simple as possible, but not simpler. Keep the scope simple.īut always have in mind: Keep It Stupid Simple. Use to understand which features you should have. In terms of systems, each portion of architecture should do its simple task. In the context of coding, the best implementation goes hand in hand with DRY (don't repeat yourself) and with refactoring. If you can not find a solution, split the problem into smaller pieces.If you can, congrats! GO TO 4 if you have other work.Think about how you could simply solve it.Take (or create if needed) the big, tough problem.You can sum up the universal and abstract implementation of the KISS (as a principle for any problem-solving) as the following: KISS saves you a lot of pain right now and even more in the future. Documentating, updating dependencies, or even portability is less demanding for cleaner stuff. Simpler, cleaner code (structure, database, or architecture) is easier to maintain, less demotivating to work on, or less painful to handover. It gets the job done (together with SMART Goals). He not only gave you the authority but also the responsibility In terms of application to Developer Experience, Johnson mentions that you should Reduce reports and other paperwork to a minimum (use KISS for your agile events), and in terms of team culture, he said let managers run their programs with a minimum of interference. You will thank yourself for solutions aiming at simplicity. Don't make your code do four things at once (at the same time). ![]() If you are designing architecture, break it into parts (from monoliths to microservices) and refactor (a lot!). If you apply the KISS principle to developer work, you should split your hard problems into smaller ones and then solve them with simple solutions. The idea behind KISS is to get results cheaper sooner and better through the application of common sense to tough problems. The phrase originally comes from the Lockheed designer team and their head engineer Kelly Johnson (later founder of the Skunk Works). Simple things are more accessible, usually easier to use, and have a flatter learning curve. Some designers use KISS as their central design goal. Broadly, it tells you that things are better when they are simpler. KISS is a principle standing for Keep It Simple, Stupid (sometimes written as Keep it stupid simple or Keep it simple and straightforward). However, achieving smart simplicity is hard on all fronts. KISS is a design principle reminding you to stop overcomplicating work.
0 Comments
Leave a Reply. |