Search results
Feb 15, 2024 · The KISS principle in Software Development, often expanded as “ Keep It Simple, Stupid,” is a design principle that advocates for simplicity in design and development processes. The core idea is to keep things as simple as possible while still achieving the desired functionality or outcome.
The KISS Principle is a Guideline that suggests to Keep Things Simple whenever possible. It was invented by Clarence Johnson during World War II. It suggests not to increase the Complexity of things as it implies adding new variables that are much more difficult to Control and Predict.
KISS, an acronym for "Keep it simple, stupid!", is a design principle first noted by the U.S. Navy in 1960. [1] [2] First seen partly in American English by at least 1938, KISS implies that simplicity should be a design goal. The phrase has been associated with aircraft engineer Kelly Johnson. [3] The term "KISS principle" was in popular use by ...
- Simple… Or Easy?
- Why Do We Need Simplicity?
- Business Complexity
- A Good Implementation Is A Deleted One
- Simple Architecture
- Don’T Try to Outsmart Your Colleagues
- Bottom to Top Development
- The Kiss Principe in A Nutshell
There are important difference between the concepts of easy and simple we need to understand first. Let’s begin with plain definitions. What the dictionary has to say about simple? Easy enough: if your system has only a few parts, you have a simple system. We could also try to define “simple” by looking at the definition of its contrary, complex: O...
Why being a software developer can be hard? One word: change. If the application you’re building will never change, stop reading this article immediately! Actually, don’t read anything about good principles in software development, it’s useless for you. Just do some procedural code in any language you want, don’t follow any principle, and you’ll su...
The complexity of a system will also be a good indicator of the amount of time developers need to add a new functionality. This is really important, business wise. Nowadays, an organization needs to have a good amount of adaptability and velocity (speed with a direction) to succeed. Yet, we can’t always avoid complexity. It’s first and foremost the...
Less code will often make your system simpler. Big is often synonym with complexity. Indeed, changing your code can have an impact on the surrounding code, and create undesired results. When you think about it, lines of code are potential technical debts, sources of bugs, triggers for headaches, screams, and tears. Show no mercy: remove every usele...
Lasagna Architecture
Lasagna is a delicious dish (when it’s well-made), but a nightmare in a codebase. The problem of a lasagna architecture? Too many layers of indirection. Let’s imagine that you have an application which simply takes some inputs from APIs, apply some business logic to transform the data and store it somewhere. Sounds reasonable, does it? Here’s what you can do. Each point is a layer: 1. APIs receiving some request. 2. Wrappers of the APIs. 3. Server factories which create the different controll...
Abstractions and Complexity
What’s an abstraction? It’s a way to deal with complexity by hiding some useless details. I wrote about it in depth in another article. For example, a function is an abstraction: when you call a function in your code, you won’t necessarily be aware of its implementation, and, as a result, its complexity. Instead, you’ll: 1. Look at the signature of the function (its name, input, and output). 2. Decide to use it or to find something better. It sounds great, right? It doesn’t matter how much co...
The Cost of Polymorphism
Polymorphism is a core concept in programming: it’s the ability of a module (class, package, and such) to take different forms. You can use the interface construct to do so, for example: Interface constructs are great, right? They allow you to swap part of your system without affecting everything around. Unfortunately, polymorphism can also bring a lot of complexity. You remember the lasagna architecture I described some paragraphs above? Many layers have interfaces for the sake of flexibilit...
As an appetizer, let me quote M. A. Jackson who wrote Principles of Program Design: It’s a common pattern I see all the time. Sometimes, we try to show how smart we are, without even realizing it. We bring design patterns in our codebases without solid reasons, and we invent clever ways to do things only the Best of the Best, the True Developer, Th...
I would like to describe a development method which push me to stay simple and as close to the requirements as I can, without going into crazy complex assumptions: bottom to top development. 1. Begin by implementing the lowest layer of your application. 2. Code onlywhat you need for your feature to work. 3. Test it. 4. Refactor your code, if necess...
This article is not meant to be an exhaustive list of everything which can bring complexity in a software. I want to show how complexity can rise quickly from many different sources. If you need to retain only one thing, it’s this: complexity needs to be considered at every stage of the life of a codebase. During design, implementation, refactoring...
Keep it simple, stupid (KISS) is a design principle which states that designs and/or systems should be as simple as possible. Wherever possible, complexity should be avoided in a system—as simplicity guarantees the greatest levels of user acceptance and interaction.
Jan 9, 2023 · 1. What is Keep it Simple, Stupid (The KISS principle)? The concept of simplicity has long been associated with sophistication, refinement, and efficiency. It’s common for artists and designers to mention its importance when creating successful works.
People also ask
What are some examples of the KISS principle?
What is the KISS principle & how can it be applied?
What is keep it simple stupid (KISS)?
What is the KISS principle in UX design?
Oct 7, 2023 · The takeaway. Let’s begin. What is the KISS principle? KISS stands for “Keep it simple, stupid!” Variations include “Keep it short (and) simple” or “Keep it simple (and) straightforward.” The KISS principle reminds us that simple solutions are often the most effective ones.
