Editing 518: Flow Charts

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 11: Line 11:
 
{{w|Flowchart|Flowcharts}} are diagrams that represent processes in a graphical form. While predominantly used in {{w|computer programming}} to visualize the structure of source code, flowcharts can in theory be used to depict any real or virtual procedure. In this comic, this idea is subverted by employing a flowchart to explain how flowcharts work. Flowcharts are a [[:Category:Flowcharts|recurring theme]] on xkcd.
 
{{w|Flowchart|Flowcharts}} are diagrams that represent processes in a graphical form. While predominantly used in {{w|computer programming}} to visualize the structure of source code, flowcharts can in theory be used to depict any real or virtual procedure. In this comic, this idea is subverted by employing a flowchart to explain how flowcharts work. Flowcharts are a [[:Category:Flowcharts|recurring theme]] on xkcd.
  
βˆ’
This seems like a faulty basis for explaining anything, but the basic functionality of flowcharts is quite intuitive, and the attempted self-description is almost unnecessary. In fact, the comic does not actually explain how to use the flowchart: it just uses an example of a very simple flowchart to demonstrate to the reader that they can easily work out how to follow it.  If the reader attempts to "game" the system by either giving contradictory answers, or refusing to acknowledge that they can see the "Yes" and "No" labels, the flowchart gets confused or becomes abusive. <strike>Just like a real computer.</strike>
+
This seems like a faulty basis for explaining anything, but the basic functionality of flowcharts is quite intuitive, and the attempted self-description is almost unnecessary. In fact, the comic does not actually explain how to use the flowchart: it just uses an example of a very simple flowchart to demonstrate to the reader that they can easily work out how to follow it.  If the reader attempts to "game" the system by either giving contradictory answers, or refusing to acknowledge that they can see the "Yes" and "No" labels, the flowchart gets confused or becomes abusive. <strikethrough>Just like a real computer.</strikethrough>
  
 
If you confirm or demonstrate that you can follow the flowchart, it inevitably leads to the "Let's go drink" box, which gives rise to the assumption that the whole chart was only a pretense for drinking.
 
If you confirm or demonstrate that you can follow the flowchart, it inevitably leads to the "Let's go drink" box, which gives rise to the assumption that the whole chart was only a pretense for drinking.

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)