User Tools

Site Tools


principles:keep_it_simple_stupid

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
principles:keep_it_simple_stupid [2016-04-07 18:40]
79.155.103.235 [Principle Statement]
principles:keep_it_simple_stupid [2016-09-04 01:00]
5.12.30.152 [Rationale]
Line 34: Line 34:
  
 The advantage of simplicity is even bigger when the person who maintains the software is not the one who once wrote it. The maintainer might also be less familiar with sophisticated programming language features. So simple and stupid programs are easier to maintain because the maintainer needs less time to understand them and is less likely to introduce further defects. The advantage of simplicity is even bigger when the person who maintains the software is not the one who once wrote it. The maintainer might also be less familiar with sophisticated programming language features. So simple and stupid programs are easier to maintain because the maintainer needs less time to understand them and is less likely to introduce further defects.
 +
 +One reason to create more complex code is to make it more flexible to accommodate further requirements. But one cannot know in what way to make it flexible or if that flexibility will be ever needed.
 +
 +"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."​ - Refactoring To Patterns - Joshua Kerievsky.
 +
 +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 
 +"Three rules of optimization":​ (1. Don't, 2. Don'​t... Yet, 3. Profile before optimizing),​ which make sense: to optimize only the code with performance problems. (First author: Michael A. Jackson)
  
  
principles/keep_it_simple_stupid.txt · Last modified: 2019-08-21 07:38 by christian