The KISS programming principle
The programming principle KISS (Keep it simple, stupid) suggests refusing to unjustifiably complicate the designed system if it is possible to make it simpler and easier.
To correctly build a system according to the KISS principle, it is necessary to adhere to the following rules:
-
All necessary tasks must be broken down into smaller subtasks, the development of which should not take more than
4-12hours. - All subtasks must be solved by one or more classes.
-
Methods for solving problems should ideally be limited to no more than
30-40lines. - Before writing code, you first need to think of what the solution to the problem will be.
- All unnecessary and obsolete code should be removed.
See also
-
principle
SOLID,
which sets guidelines for OOP-based software -
principle
DRY,
which is the division of software into small components -
principle
YAGNI,
which involves the rejection of redundant software functionality -
principle
CQS,
which specifies only one command for each function -
principle
LoD,
which is used in software development -
responsibility separation principle,
which is used in software development