KISS is a design principle reminding you to stop overcomplicating work. It is better to keep things simple. However, achieving smart simplicity is hard on all fronts.
What Is KISS
KISS is a principle standing for Keep It Simple, Stupid (sometimes written as Keep it stupid simple or Keep it simple and straightforward). Broadly, it tells you that things are better when they are simpler. Some designers use KISS as their central design goal. Simple things are more accessible, usually easier to use, and have a flatter learning curve.
The phrase originally comes from the Lockheed designer team and their head engineer Kelly Johnson (later founder of the Skunk Works). The idea behind KISS is to get results cheaper sooner and better through the application of common sense to tough problems. If it works, don’t fix it.
Source: Kiss Visually
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. If you are designing architecture, break it into parts (from monoliths to microservices) and refactor (a lot!). Don't make your code do four things at once (at the same time). You will thank yourself for solutions aiming at simplicity. 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. He not only gave you the authority but also the responsibility
Why You Might Want KISS
It gets the job done (together with SMART Goals). Simpler, cleaner code (structure, database, or architecture) is easier to maintain, less demotivating to work on, or less painful to handover. Documentating, updating dependencies, or even portability is less demanding for cleaner stuff. KISS saves you a lot of pain right now and even more in the future.
Problems the KISS Helps to Solve
- Demotivated team
- Increased cost
- Bad product-market fit
- Sunk Cost
- Poor Code Quality
- Unnecessary features
How to Implement KISS
You can sum up the universal and abstract implementation of the KISS (as a principle for any problem-solving) as the following:
- Stop to gather information.
- Take (or create if needed) the big, tough problem.
- Think about how you could simply solve it.
- Try to find a simple solution.
- If you can, congrats! GO TO 4 if you have other work.
- If you can not find a solution, split the problem into smaller pieces. GO TO 4.
In the context of coding, the best implementation goes hand in hand with DRY (don't repeat yourself) and with refactoring.
In terms of systems, each portion of architecture should do its simple task. Use [YAGNI] to understand which features you should have. Keep the scope simple.
But always have in mind: Keep It Stupid Simple.
Common Pitfalls of KISS
- Simple being seen as stupid. To quote Einstein: Everything should be as simple as possible, but not simpler. Simple solutions are not bad or lacking to solve complex issues (you should not have a complex issue in the first place, split it!)
- Simple as the final answer to everything, without thinking. There are some tasks that you can not solve only through KISS recursion (split-solve cycle) alone. Sometimes, keeping the big picture is vital, or splitting is not possible. However, with these things (Like business strategy), you can split your solution into simple steps. Doing so gives you actionable things to do.
Resources for KISS
Want to write for DXKB?
Feel free to contribute. People from DXKB community will be more than happy.
Total responsibility for failure is a difficult thing to accept, and taking ownership when things go wrong requires extraordinary humility and courage.Read more
Responsibility is about trusting people and their commitment towards the work assigned. A responsible person completes the task assigned to them no matter what the circumstances are.Read more
The Waterfall methodology is a linear project management approach where customer's requirements are collected at the beginning of the project. Then a sequential project plan is created to satisfy those requirements. The concept is appropriate for small and clear projects.Read more
Release management is the process of managing, planning, designing, scheduling, testing, controlling and deploying of a software build through different stages and environments; in preparation for software releases.Read more