The simpler the explanation and the simpler the product, the more likely it is that the output will be useful to others. They care about being able to take that person’s output and make it useful to their own lives. Ideally, however, the state shown on the left side of the figure should never occur.It was Albert Einstein who said “If you can’t explain it, you don’t understand it well enough.” Though it is often mis-reported as being “If you can’t explain it to a six year old, you don’t understand it well enough.” What Einstein was driving at was a particular application of “keep it simple, stupid”.įrom scientific concepts to products the end-user doesn’t care how clever the creator or designer of something is. By splitting the method M into three methods,Įach with less than 100 statements and a maximum nesting depth of 5 levels, manageable modularization units were created, which follow the rules forĬomplexity, and allow the required modification to be made. The result is illustrated on the right of the figure. So complex that it was practically impossible to make another necessary change, and the developer was forced to refactor in line with the KISS principle. Reached the state shown on the left after continuous additional developments. The method, which is only illustrated schematically, is a real example from a live ABAP program, which The method consists of approximately 160 statements and reaches a The figure below shows the structure of a method that does not follow the KISS principle. Comprehensive unit tests can ensure that a program behaves in the same way after the refactoring process.
KISS KEEP IT SIMPLE STUPID CODE
The refactoring of existing code is supported by the required coverage by Refactoring of an existing program is not only useful for following the above rule, but also for all following rules. Understandability, maintainability, and extensibility, as well as considerably reducing the relatedĮffort for troubleshooting and functional enhancements (see Wikipedia entry on refactoring). Improving the structure of programs while retaining the observable program behavior.
Refactoring refers to the process of manually or automatically If existing programs do not follow the KISS principle, and these programs need to be further developed, Structure and style of programs, in particular Rules that support this approach relate to the To develop according to the KISS principle, you should ensure right from the start that the complexity of the program remains manageable. Programs that were initially simple thus become ever more complex, although this is not justified by the complexity of the task at hand. New functions together, new functions are simply added (usually using IFĬontrol structures) to old functions. Instead of creating new implementations for old and Programs are maintained for lengthy periods.This can be due to poor design or simply a rash, undisciplined programming style. Programs are too complex right from the start.There are plenty of bad examples of the KISS principle. The best solution to a problem is usually the one that is as simple, minimalist, and easy to understand as possible, while ensuring stability, understandability, and maintainability in addition to functional correctness.
The preferred theory is the one that makes fewest assumptions to explain observations (see Wikipedia entry on the KISS principle).įollow the KISS principle, and limit the complexity of your programs as far as possible. The basic statement of the KISS principle is similar to Occam’s razor, which says that in science KISS is an acronym and can have any of the following meanings (the list is not exhaustive): The KISS principle says that you should always choose the simplest solution for a problem. SAP NetWeaver AS ABAP Release 751, ©Copyright 2017 SAP AG.
0 kommentar(er)
