principles:keep_it_simple_stupid
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
principles:keep_it_simple_stupid [2018-12-30 05:21] – [Evidence] fixing a few of the grammar mistakes 72.178.89.198 | principles:keep_it_simple_stupid [2020-10-12 12:41] – old revision restored (2020-01-20 17:26) 159.69.186.191 | ||
---|---|---|---|
Line 15: | Line 15: | ||
* [[contexts: | * [[contexts: | ||
* [[contexts: | * [[contexts: | ||
- | ===== Principle Statement ===== | + | ===== Principle Statement =====l |
A simple solution is better than a complex one, even if the solution looks stupid. | A simple solution is better than a complex one, even if the solution looks stupid. | ||
Line 26: | Line 26: | ||
A solution that follows the KISS principle might look boring or even " | A solution that follows the KISS principle might look boring or even " | ||
- | This does not mean that features like inheritance and polymorphism should not be used at all. Rather they should only be used when they are necessary or there is some substantial advantage | + | This does not mean that features like inheritance and polymorphism should not be used at all. Rather they should only be used when they are necessary or there is some substantial advantage |
- | + | ||
===== Rationale ===== | ===== Rationale ===== | ||
Line 39: | Line 37: | ||
"When you make your code more flexible or sophisticated than it needs to be, you over-engineer it. Some do this because they believe they know their system’s future requirements. They reason that it’s best to make a design more flexible or sophisticated today, so it can accommodate the needs of tomorrow. That sounds reasonable, if you happen to be a psychic." | "When you make your code more flexible or sophisticated than it needs to be, you over-engineer it. Some do this because they believe they know their system’s future requirements. They reason that it’s best to make a design more flexible or sophisticated today, so it can accommodate the needs of tomorrow. That sounds reasonable, if you happen to be a psychic." | ||
- | Another reason to create more complex code is to make optimizations. An optimized code is a more complex code. Pareto principle applies also in code: a program spend most of the time in a small portion of the code, so it will be wise to concentrate the effort to optimize only that part of the code. Another best practice is the to follow the | + | Another reason to create more complex code is to make optimizations. An optimized code is a more complex code. Pareto principle applies also in code: a program spend most of the time in a small portion of the code, so it will be wise to concentrate the effort to optimize only that part of the code. Another best practice is to follow the |
"Three rules of optimization": | "Three rules of optimization": | ||
principles/keep_it_simple_stupid.txt · Last modified: 2021-10-20 21:09 by christian