Differences

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

--- principles:keep_it_simple_stupid [2025-11-04 22:52] – created luciennej68
+++ principles:keep_it_simple_stupid [2025-11-25 10:53] (current) – old revision restored (2021-10-20 21:09) christian
@@ Line 1: / Line 1: @@
-Waiting times can be reduced when the number of staff could be increased for busier time periods. Perhaps weekends won' because the busiest time of the week, and summer time won't end up being busiest year.
+====== Keep It Simple Stupid (KISS) ======
-When you look at today's health care climate, things are looking pretty scary. Expenses are at an all-time high and continue to rise, while health is in an all-time low and continues to decline. It is widely known i always are within a crisis and wish to undertake it. We have taken action for a insurance side by creating the Affordable Care Act or ACA, which we refer to as Healthcare Reform.
+===== Variations and Alternative Names =====
-Doctors are breaking even with Medicare patients and cannot survive these people do not have access to enough regular insurance people. Many are planning on quitting the profession if for example the new 新潟市中央区 肩こり plan is implemented this is because cannot are in business with its regulations. Is going to also mean a lack of doctors and long waiting lines for patients. Obama kills jobs, Romney creates them.
+  * (Rule of) Simplicity
+  * KISS may also mean "Keep it short and simple", "keep it simple and straightforward", "keep it smart and simple", etc. A large amount of variations exists.
-They monitor the performance of a hospital or surgery, and it's also possible to determine at a search how well the hospital or surgical procedures are doing. Whether or not be the surplus of nurses, or the department may have find you are out of beds, or need other articles.
+**Remarks**: "Stupid" may be interpreted as an adjective or a noun. Compare the two variants "keep it simple and stupid" vs. "keep it simple, stupid!". Despite all these alternative names, the general idea of the KISS principle is always the same.
-Of course, the issue with this is pretty obvious. With a discount healthcare plan, you've to pay for your expenses out-of-pocket. On the upside, means positivity . do pay, the bill will be extremely incredibly low. Some people receive discounts of 50 percent or more with these kinds of plans. If you go to your doctor examination actually year, this is simply not a bad deal. A visit that costs $200 may discounted to $100, for the way generous the program was. True, you don't have insurance, however, you were still able in order to $100. Should you have had nothing available, you wouldn't experience any savings a person would need to pay the full amount.
-You ought to look to the news related to the industry. You will also where possible find the actual companies will be hiring the healthcare contractors. If you need it in acquiring a transfer from one industry to your 新潟市中央区 肩こり you'll be able to must first of all find out the qualities which is fruitful for your health companies.
+===== Context =====
-Acupuncture for back pain can be very very effective. After the first treatment he reported that discomfort was more pleasant and that he can sit a little longer. Since any Acupuncture clinic will likely ask anyone to do numerous visits we got him again and found that he nonetheless feeling just better. After three visits his pain was reduced greatly and his golf game was back again again. After five visits he can sit for a extended period of time than he has in a few months. The real story here is always that the man is in his late seventies!
+  * [[contexts:Object-Oriented Design]]
+  * [[contexts:Architecture]]
+  * [[contexts:User Interface Design]]
+  * [[contexts:Implementation]]
-Big government has won and free market has lost on this one. But honestly, totally free whataburger coupons market folks did not care or give one thought towards the uninsured. I really believe a free market is key for a remarkable growing economy, but once we let people starve typically the streets, it isn't worth getting this done.
+===== Principle Statement =====
-All [[http://shop.Ororo.co.kr/bbs/board.php?bo_table=free&wr_id=4438524|新潟市中央区 肩こり]] problems the family faces can be dealt which has. But the price doing so makes it hard to obtain the right quality of ears ringing individuals. Is undoubtedly the choice of availing health insurance policies to scale back the price family healthcare. But issue is which have the inclination to get the right health insurance plan for family members but simply get confused in selecting the right some.
+A simple solution is better than a complex one, even if the solution looks stupid.
-As far as pick up lines are concerned, I do think I took care in the worst culprits. And as for dating tips for men, We are back with additional of those involved with the subsequent. In the meantime, I'd love a guy's watch. What are your flirting "Do's" and "Don'ts"?
-You choose to go the Acupuncture clinic lot of coaching as well as tutoring. It is very important to begin your career with a normal healthcare professional. Some of the pros begin their career as health aides. They usually look at the homes.
+===== Description =====
-Income Security outlays elevated from 2001 to 2010 by 306%. The dollar value from the increase is produced by 143.1 billion to 437.7 billion. Because this category included unemployment payments, that could be pointed to as nicely driver of this increase. Utilizing the 3% yearly increase, always be make the rise from 143.1 billion in 2001 to 186.7 million. This would provide 251 billion per year in cost.
+The KISS principle is about striving for simplicity. Modern programming languages, frameworks and APIs have powerful means to create sophisticated solutions for various kinds of problems. Sometimes developers might feel tempted to write "clever" solutions that use all these complex features. The KISS principle states that a solution is better when it uses less inheritance, less polymorphism, fewer classes, etc.
-I have gotten over many years that really government program has begun it can never be reduced or long gone. Once people tend to be hired to face government deals, they won't ever be run. Big buildings get constructed to deal with thousands of bureaucrats who'll have better pay and benefits than their counterparts in the individual sector. 新潟市中央区 肩こり represents 1/6th of our economy too is about to be moved into the hands of government. Picture it upward being a bad idea? Benefit is for sure, just about be no turning back in time.
+A solution that follows the KISS principle might look boring or even "stupid" but simple and understandable. The KISS principle states that there is no value in a solution being "clever" but being easily understandable.
+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 =====
+A simpler solution is better than a complex one because simple solutions are easier to maintain. This includes increased readability, understandability, and changeability. Furthermore, writing simple code is less error-prone.
+The advantage of simplicity is even more significant 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 how 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. The reason that it's best to make a design more flexible or sophisticated today is to 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 spends 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)
+===== Strategies =====
+This is a very general principle, so there is a large variety of possible strategies to adhere more to this principle largely depending on the given design problem:
+  * Avoid inheritance, polymorphism, dynamic binding and other complicated OOP concepts. Use delegation and simple if-constructs instead.
+  * Avoid low-level optimization of algorithms, especially when involving Assembler, bit-operations, and pointers. Slower implementations will work just fine.
+  * Use simple brute-force solutions instead of complicated algorithms. Slower algorithms will work in the first place.
+  * Avoid numerous classes and methods as well as large code blocks (see [[More Is More Complex]])
+  * For slightly unrelated but rather small pieces of functionality use private methods instead of an additional class.
+  * Avoid general solutions needing parameterization. A specific solution will suffice.
+  * ...
+===== Caveats =====
+See section [[#contrary principles]].
+===== Origin =====
+The principle was coined by the American engineer Kelly Johnson referring to the requirement that a military aircraft should be repairable with a limited set of tools under combat conditions ((Ben R. Rich: //[[http://www.nap.edu/html/biomems/cjohnson.pdf|Clarence Leonard (Kelly) Johnson 1910—1990: A Biographical Memoir]]//)).
+The principle of striving for simple solutions sometimes is also called "(rule of) simplicity"((Eric S. Raymond: //[[http://www.catb.org/~esr/writings/taoup/html/ch01s06.html#id2877917|The Art of Unix Programming]]//)) which was also prominently stated by Tony Hoare in his Turing Award lecture: "I conclude that there are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult."((Tony Hoare: //[[http://awards.acm.org/images/awards/140/articles/4622167.pdf|The Emperor’s Old Clothes / The 1980 ACM Turing Award Lecture]]//))
+===== Evidence =====
+/* Comment out what is not applicable and explain the rest: */
+/*  * [[wiki:Proposed]]*/
+/*  * [[wiki:Questioned]]*/
+[[wiki:Accepted]]: This principle is widely known and accepted in practice. See for example Jargon File: //[[http://www.catb.org/jargon/html/K/KISS-Principle.html|KISS Principle]]//
+[[wiki:Examined]]: While the preference for simple solutions can be considered trivially intuitive, there has been some work relating simplicity or rather complexity and certain quality attributes. But as there is no universally applicable complexity metric and not even a commonly agreed upon clear definition of simplicity, research is bound to examine certain aspects of KISS independently.
+The following hypotheses can be stated:
+  - Simpler solutions are faster to implement.
+  - Simpler solutions yield fewer implementation faults (which reduces testing effort).
+  - Simpler solutions are easier to maintain, i.e. detecting and correcting defects is more effective and efficient.
+  - Simpler solutions yield more reliable software, i.e. fewer defects show up after releasing the software.
+All these hypotheses can be examined with respect to different complexity metrics.
+Hypothesis 1 is true by definition. If the solution cannot be implemented quickly, it is not simple.
+Though hypotheses 2 and 3 are not true by definition but they can be regarded intuitively clear. Nevertheless, there is some research. In ((Virginia R. Gibson and James A. Senn: //[[http://dl.acm.org/citation.cfm?id=62073|System Structure and Software Maintenance Performance]]//)) a system was improved in two steps resulting in three variants of the same system. Several metrics show that the improvements reduced complexity. 36 programmers with varying experience conducted three different maintenance tasks and their performance was measured. The results indicate that the improvements also improved maintainability. Several other studies support the correlation between complexity and maintainability((Chris F. Kemerer: //[[http://link.springer.com/article/10.1007%2FBF02249043?LI=true|Software complexity and software maintenance: A survey of empirical research]]//)).
+Furthermore, software cost estimation techniques are partly based on complexity judgments((Barry W. Boehm: //Software Engineering Economics//, IEEE)). So complexity---although this normally relates the complexity of the problem and not to the complexity of the solution---is a known cost factor which may be accounted to maintenance.
+Lastly, hypothesis 4 is likely to be false. Several studies relating complexity metrics and post-release reliability show that module size in lines of code predicts reliability at least as good as the McCabe metric (also called cyclomatic complexity) ((see Albert Endres, Dieter Rombach: //A Handbook of Software and Systems Engineering//, p. 168ff.)). Assuming cyclomatic complexity correctly depicts the complexity of a module, reliability should not the reason for applying KISS.
+===== Relations to Other Principles =====
+==== Generalizations ====
+==== Specializations ====
+  * [[More Is More Complex]] (MIMC): KISS states that one should strive for simplicity. MIMC makes this more concrete stating that more of anything (methods, classes, lines of code, ...) increases complexity.
+  * [[You Ain't Gonna Need It]] (YAGNI)
+  * [[Rule of Parsimony]]
+  * [[Rule of Robustness]]
+==== Contrary Principles ====
+Note that many principles are contrary to KISS. This means that it is worthwhile to consider KISS when considering one of those. Nevertheless this does not mean that this is true the other way around. When considering KISS, one wouldn't want to consider all principles that have complexity as a disadvantage. So here are those needing consideration:
+  * **[[Generalization Principle]] (GP)**: This is the directly converse principle. A generally applicable solution typically is not simple anymore.
+  * **[[Murphy's Law]] (ML)**: The ultimate reason behind KISS is to increase maintainability and reduce the introduction of defects. But following KISS blindly by always using the simplest solution may also lead to //reduced// maintainability when Murphy's Law is not considered.
+  * [[Model Principle]] (MP): There are often simpler ways to build a software system than to model and mirror the real-world behavior, which frequently means having more objects and more complicated structures. Nevertheless, it is advisable to do so anyway.
+==== Complementary Principles ====
+==== Principle Collections ====
+{{page>collections:OOD Principle Language#Box}}
+{{page>collections:Unix Philosophy (Eric S. Raymond)#Box}}
+===== Examples =====
+==== Example 1: Fuzzy Simplicity ====
+Simplicity is a blurry, partly subjective measure. Sometimes it is difficult to tell what is simpler. The following example shows that:
+<code java>
+public String weekday1(int dayOfWeek)
+{
+    switch (dayOfWeek)
+    {
+        case 1: return "Monday";
+        case 2: return "Tuesday";
+        case 3: return "Wednesday";
+        case 4: return "Thursday";
+        case 5: return "Friday";
+        case 6: return "Saturday";
+        case 7: return "Sunday";
+        default: throw new IllegalArgumentException("dayOfWeek must be in range 1..7");
+    }
+}
+public String weekday2(int dayOfWeek)
+{
+    if ((dayOfWeek < 1) || (dayOfWeek > 7))
+        throw new IllegalArgumentException("dayOfWeek must be in range 1..7");
+    final String[] weekdays = {
+        "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", "Sunday"};
+    return weekdays[dayOfWeek-1];
+}
+</code>
+Both methods do exactly the same thing. They return a string representing the weekday. Just the implementation is different. Both versions may be seen as simpler than the other depending on the view taken. ''weekday2'' has less statements and less execution branches. Complexity metrics measuring these aspects (e.g. the [[glossary:cyclomatic complexity]]) will therefore prefer ''weekday2''.
+On the other hand ''weekdays1'' uses less language features (just switch, return, and exceptions whereas ''weekdays2'' needs if, arrays, arithmetic, return, and exceptions). Furthermore in ''weekdays1'' the relation between input and output can be seen directly and it's clear how it works by just seeing the method. But for understanding ''weekday2'' there are more details to think about. This is especially true for the range check at the beginning and the index computation in the ''return'' statement. Clearly this is not particularly difficult but these are aspects which are more difficult than in the other version of the method.
+So it's not objectively clear which of the two implementations KISS prefers without saying which complexity metric to apply. But this ambiguity is not a problem since principles are not meant to be unambiguous and objective. Eventually a human developer has to decide which solution to implement and the principles only give guidelines.
+===== Description Status =====
+/* Choose one of the following and comment out the rest: */
+/*[[wiki:Stub]]*/
+[[wiki:Incomplete]]
+/*[[wiki:Complete]]*/
+===== Further Reading =====
+  * [[wiki>KeepItSimple]]
+  * [[wp>KISS principle]]
+  * [[http://people.apache.org/~fhanik/kiss.html|Apache: KISS]]
+  * [[http://www.catb.org/~esr/writings/taoup/html/ch01s06.html#id2877917|The Art of Unix Programming: Rule of Simplicity]]
+===== Discussion =====
+Discuss this wiki article and the principle on the corresponding [[talk:principles:Keep It Simple Stupid|talk page]].