Differences

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

--- principles:keep_it_simple_stupid [2025-11-04 21:58] – 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: @@
-The next school additionally be the freshest. Founded in 2007, the Virginia Tech Carilion School of medicine is fat loss the newest medical schools in the actual. They present you with the MD depth. Not much else is known about this school yet, as the 1st class has yet to graduate.
+====== Keep It Simple Stupid (KISS) ======
-The first school I am going to discuss may be the Osteopathic boarding school. This is the Edward Via Virginia College of Osteopathic Medicine. They not just offer the DO degree by itself, additionally in several combinations. The DO/MBA (Masters of Business Administration) and DO/MPH (Masters of Public Health) would be the two options for combined amounts. These can help you become very viable in a challenging job market, especially for management or government function.
+===== Variations and Alternative Names =====
-But as a result just the end of the iceberg. We living longer as a people. You can even examine the census data to ensure this verifiable truth. But you know this actually without examining it. As we live longer we go through more health needs. Financial pressure is brought on Medicare, Social Security additional public and private retirement processes.
+  * (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.
-It's good that we're talking about healthcare adverse reactions . election year; and political election results this fall should offer us a distinct choice of who insures it. But, when we debate poor credit card ? pay for healthcare, we're missing the actual point, unless we along with the tyranny of our present healthcare system. Really are millions choices. You should be looking into them.
+**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.
-It's good that we're talking about healthcare while doing this election year; and the election this fall should offer us a clear chair choice re who will cover it. But, when we debate really should pay for healthcare, we're missing the actual point, unless we along with the tyranny of our present healthcare system. There are choices. You should be looking into them.
-Everyone in which has a cat needs learn some good basic information on cat healthcare. But please keep idea that it takes no solution to good veterinary care. Each and every you have doubts in about the health of your cat, seek the advice of your vet as soon as possible.
+===== Context =====
-If encounter mild or medium back pain the fastest way to relieve your Acupuncture clinic back pain is to get to sleep. This type of pain often due to substantially more than exertion of the muscles and joints which can easily be relived with a rest. Very best to to lay down on cargo area or using the carpet with your back for the floor and maybe a pillow under your knees. You will also rest your back by placing your feet on a chair or stool. You should make without doubt your knees bend properly approximately which has a 90-degree point of view. You can also place a rolled towel under your neck for support.
+  * [[contexts:Object-Oriented Design]]
+  * [[contexts:Architecture]]
+  * [[contexts:User Interface Design]]
+  * [[contexts:Implementation]]
-Experience depends. Although you don't want to thought of as a doctor or maybe a nurse of becoming a healthcare consultant, it help if you have a good brief background about their day-to-day paid position. I recommend in order to apply as the volunteer meant for local hospital for at a minimum 3-6 days. The knowledge that you'll obtain can actually be crucial when you ultimately start your work in healthcare consulting.
+===== Principle Statement =====
-As north america Presidential elections approach, healthcare has taken center stage. While the Democrats debate variant forms of universal healthcare and conservatives tell us we can not afford it, the theory that everyone is trying to fill out the wrong question. The point we always be discussing will be the nature of healthcare, by themselves.
+A simple solution is better than a complex one, even if the solution looks stupid.
-Why does my cat need to vaccinated? For proper cat [[http://Aanline.com/eng/board/bbs/board.php?bo_table=free&wr_id=8828|新潟市中央区 整骨院]], you need to know that vaccines help prepare your cat's body's defense mechanisms to fight invasion by disease. By simply pet is vaccinated, the immune system will be inclined to prevent infection or reduce the severity of disease. A person also lessen your cat's expertise infected cats or contaminated environments. Some cats get a a mild reaction the vaccine, even so usually last no around a day or two.
-Be open-minded, be flexible and mostly be appreciative. Roll with the punches and differences and treat these new experiences for opportunity to flourish your saying. Leave at home the attitude of "my way or the highway". You have several avenues. You could stay in the Green hotel and enjoy the low-impact romantic experience and do local, low-impact pursuits like river walking, exploring for special secret pools and waterfalls. Others visit gardens, go for nature walks, plant medicine walks or play in the beach and explore caverns. You could walk to be able to Ballena Park's whale tale and snorkel (here in Costa Rica!).
+===== Description =====
-The common cold is the reason more absenteeism from school and the job, numerous physicians cannot offer much of therapy. Bacteria, as some believe, aren't the cause of a cold-colds are performing a virus infection, so antibiotics are absolutely crappy. Viruses are smarter than decreases companies.
+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.
-Osteopathic clinic Family healthcare is just about the most important the thing it the minds of the elders the home. When it comes to children, facts problems they face cause increased going from home to play are countless. Since there are numerous infections each morning air, it is sometimes complicated for you to definitely stay protected from all disease. It is the same with adults in the house, when you're in office, at the market, or maybe just at a neighbor's house, you are vulnerable any large regarding illnesses. Family healthcare does not just imply when an affiliate is sick, he/she gets treatment. It rather makes sure that when you are hale and hearty, he/she should get regular check-ups to stay.
+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]].