Editing 1691: Optimization

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 8: Line 8:
  
 
==Explanation==
 
==Explanation==
−
In computing, {{w|program optimization}} is the practice of making a computer program work as quickly as possible, typically by designing it to perform the fewest calculations. "{{w|Premature optimization}}" is the practice of trying to optimize parts of a program before such optimization has been shown to be needed. Optimization can prove to have been a waste of time if parts of the program are later changed or discarded, or if the optimized code is only a small part of the workload. Making a routine 10 times faster doesn't help much if that routine is only consuming 1% of the running time to begin with and it may result in more complicated and buggier code.
+
{{incomplete|No title-text explanation}}
 +
This comic is a flowchart making fun of the difference between prematurely optimizing and just doing things right. Since you're consulting a flowchart to answer, you're prematurely optimizing.
  
−
This comic is a flowchart making fun of the difference between prematurely optimizing and doing things right in the first place: it tells you that if you are using it to decide whether you are optimizing prematurely, then you're optimizing prematurely. The humorous conclusion is that if there is any doubt whether an optimization is ''premature'', then it is ''premature''!
+
Donald Knuth in his paper "Structured Programming with Goto statements" said:
−
 
 
−
Another layer of humor is provided by the minimalism and directness of the flowchart, which suggests that it has itself been (prematurely?) optimized.
 
−
 
 
−
The title text's ''root of all evil'' refers to {{w|Donald Knuth}}'s paper "Structured Programming with Goto statements" (1974)<ref name="p261-knuth.pdf">Computing Surveys, Vol 6, No 4, December 1974: http://web.archive.org/web/20130731202547/http://pplab.snu.ac.kr/courses/adv_pl05/papers/p261-knuth.pdf</ref> in which he wrote:
 
 
<blockquote>
 
<blockquote>
 
"There is no doubt that the grail of efficiency leads to abuse. Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time: '''premature optimization is the root of all evil'''. Yet we should not pass up our opportunities in that critical 3%."
 
"There is no doubt that the grail of efficiency leads to abuse. Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time: '''premature optimization is the root of all evil'''. Yet we should not pass up our opportunities in that critical 3%."
 
</blockquote>
 
</blockquote>
−
The title text takes the joke a step further by proposing optimizing a brand new project by introducing a procedure to determine whether a possible optimization is premature - which is obviously a premature optimization. It pokes fun at time-wasting behavior by obsessively perfectionist coders who develop tools to analyze aspects of their software, such as performance. In some fields, such as compilers or database design, such tools can be useful and productive (the 3% mentioned by Knuth?), but the usage suggested here is more appropriately covered by instinct, common sense, and observation of the behavior of the completed program. Knuth's quote itself is a play off of a verse from the Bible, where Paul tells Timothy "[...] the love of money is the root of all evil" (https://biblehub.com/1_timothy/6-10.htm)
 
  
−
The title text may also be poking fun at the comic, since the comic itself may be the "system" used to determine premature optimization.
+
Source: http://web.archive.org/web/20130731202547/http://pplab.snu.ac.kr/courses/adv_pl05/papers/p261-knuth.pdf (Computing Surveys, Vol 6, No 4, December 1974)
  
−
Flowcharts are [[:Category:Flowcharts|often used in xkcd]] including the (mostly) non-farcical [[1688: Map Age Guide]] one week prior to this comic. Inefficiency (another xkcd theme) was featured in the [[1690: Time-Tracking Software|comic prior to this one]].
+
The title text describes another time-wasting behaviour common in obsessively perfectionist coders: developing tools to analyse aspects, such as performance, of the software actually required. In the some fields, such as compilers or database design for instance, such tools are useful and productive, but the usage suggested here is more appropriately covered by instinct and common sense.
  
 
==Transcript==
 
==Transcript==
−
:[A flow chart is shown with three boxes connected with two arrows. The first box is rectangular:]
+
:[A flow chart is shown with three boxes connected with two arrows. The first box rectangular:]  
−
:Are you '''''prematurely optimizing''''' or just '''''taking time to do things right?'''''
+
:Are you prematurely optimizing or just taking time to do things right?
  
 
:[From the first box there is a short arrow straight down to a diamond shaped box:]
 
:[From the first box there is a short arrow straight down to a diamond shaped box:]
 
:Are you consulting a flowchart to answer this question?
 
:Are you consulting a flowchart to answer this question?
  
−
:[A labeled arrow continues down.]
+
:[An arrow labeled "Yes" continues down to the last box, which is rectangularly shaped.]
−
:Yes
 
−
 
 
−
:[The arrow connects to the final rectangular box.]
 
 
:You are prematurely optimizing
 
:You are prematurely optimizing
  
−
==References==
+
{{comic discussion}}
−
<references />
 
  
−
{{comic discussion}}
 
 
[[Category:Flowcharts]]
 
[[Category:Flowcharts]]
−
[[Category:Time management]]
 

Please note that all contributions to explain xkcd may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see explain xkcd:Copyrights for details). Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel | Editing help (opens in new window)

Templates used on this page:

Retrieved from "https://www.explainxkcd.com/wiki/index.php/1691:_Optimization"