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
principles:keep_it_simple_stupid [2019-11-20 15:53]
41.33.203.115 old revision restored (2019-11-20 15:40)
principles:keep_it_simple_stupid [2019-12-03 16:25] (current)
194.156.152.76 remove unneeded "the"
Line 37: 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."​ - Refactoring To Patterns - Joshua Kerievsky. "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 +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":​ (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) "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-12-03 16:25 by 194.156.152.76