Editing 844: Good Code
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 14: | Line 14: | ||
Additionally, the humorous point is being further emphasized for the primary target audience, programmers, by using an {{w|infinite loop}} - or more precisely, 2 possible loops and 1 forced loop in the flowchart itself. | Additionally, the humorous point is being further emphasized for the primary target audience, programmers, by using an {{w|infinite loop}} - or more precisely, 2 possible loops and 1 forced loop in the flowchart itself. | ||
− | Also, of particular note, is the fact that Randall (the author) drives home the point of the inescapability of the infinite loop(s) by the use of the additional, disconnected, and logically unreachable portion of the flowchart. This disconnect points out that the only way to actually get to "Good Code" using the flow chart would be to follow a path of actions — which does '''not''' start at the | + | Also, of particular note, is the fact that Randall (the author) drives home the point of the inescapability of the infinite loop(s) by the use of the additional, disconnected, and logically unreachable portion of the flowchart. This disconnect points out that the only way to actually get to "Good Code" using the flow chart would be to follow a path of actions — which does '''not''' start at the proscribed place — for which there is only an unknown and possibly unknowable starting action which no one has ever discovered previously. |
− | The title text, "You can either hang out in the Android Loop or the HURD loop," makes a dig at | + | The title text, "You can either hang out in the Android Loop or the HURD loop," makes a further dig at each community, claiming that Android developers are always choosing fast, ugly code, while HURD developers are always choosing to "do things right" but can therefore never finish their project at all. The [http://www.gnu.org/software/hurd/ GNU Hurd project], which aims to create the kernel (i.e. lower-level portions) of the "GNU operating system," while building on a number of fundamentally "beautiful" concepts, has nonetheless been in development for many years with little forward motion towards actual usability by anyone except the developers themselves. |
− | |||
− | The [http://www.gnu.org/software/hurd/ GNU Hurd | ||
Finally, the [https://xkcd.com/844/info.0.json official transcript] of this comic is itself somewhat humorous (an additional {{w|In-joke|inside joke}}, if you will) in that it converts the flowchart into a simple list of instructions (aka pseudo-code) using numbered lines as reference points for identifying which instruction to read and follow next. This process is basically identical to the oft-maligned programming technique of using so-called "{{w|Goto|goto loops}}." — Furthermore, there is also a slight cross-reference between infinite loops and goto loops which is probably being referenced, in that goto loops are often criticized (whether accurately or not) as being more likely to create unintended infinite loops in code... primarily because of the difficulty inherent in keeping track of possible entry and exit paths, especially when making edits to the code at a later time. | Finally, the [https://xkcd.com/844/info.0.json official transcript] of this comic is itself somewhat humorous (an additional {{w|In-joke|inside joke}}, if you will) in that it converts the flowchart into a simple list of instructions (aka pseudo-code) using numbered lines as reference points for identifying which instruction to read and follow next. This process is basically identical to the oft-maligned programming technique of using so-called "{{w|Goto|goto loops}}." — Furthermore, there is also a slight cross-reference between infinite loops and goto loops which is probably being referenced, in that goto loops are often criticized (whether accurately or not) as being more likely to create unintended infinite loops in code... primarily because of the difficulty inherent in keeping track of possible entry and exit paths, especially when making edits to the code at a later time. |