Editing 1833: Code Quality 3

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 30: Line 30:
 
In the final panel, Ponytail references {{w|leet|leet-speak}}, in which symbols are replaced with similar-looking symbols, and a {{w|manifesto}}, a statement of a person or group's beliefs and intentions. A manifesto from a survivalist cult leader might be nonsensical, even before being translated to leet-speak. Memory allocation is a low-level computer programming concept; most modern languages have features that take care of memory allocation for the programmer, possibly implying that Cueball does not know how to use these features.
 
In the final panel, Ponytail references {{w|leet|leet-speak}}, in which symbols are replaced with similar-looking symbols, and a {{w|manifesto}}, a statement of a person or group's beliefs and intentions. A manifesto from a survivalist cult leader might be nonsensical, even before being translated to leet-speak. Memory allocation is a low-level computer programming concept; most modern languages have features that take care of memory allocation for the programmer, possibly implying that Cueball does not know how to use these features.
  
βˆ’
At this point Cueball, quickly becoming impatient with Ponytail's sass in what is supposed to be a formal code review, retorts that if she can't start giving him the constructive criticism that he's looking for, he can always find someone else to replace her. Ponytail smugly responds that nobody else would be able to stomach his code for more than one sitting, and that she's the only one he's got.
+
At this point Cueball, quickly becoming impatient with Ponytail's sass, retorts that if she can't start giving him the constructive criticism that he's looking for, he can always find someone else to replace her. Ponytail smugly responds that nobody else would be able to stomach his code for more than one sitting, and that she's the only one he's got.
  
 
{{w|Forth_(programming_language)#Programmer.27s_perspective|Forth}} is an old programming language that tends to be difficult to read. It is stack-based, meaning that values to be operated on are moved on a {{w|Stack (abstract data type)|stack}} before the operation to be performed is given. Using stacks can be considered different from programming languages that resemble natural human language (e.g. {{w|COBOL}}). While stack-based computing makes some problems very simple (for example, it is relatively simple to design a Forth compiler, or reversing the order of an array) and uses less computing resources, such programming languages are not easy to learn. Since Forth allows the programmer to rewrite the language, or define their own language, and it does not enforce restrictions like data types, it may be especially easy for novices to write cryptic code.
 
{{w|Forth_(programming_language)#Programmer.27s_perspective|Forth}} is an old programming language that tends to be difficult to read. It is stack-based, meaning that values to be operated on are moved on a {{w|Stack (abstract data type)|stack}} before the operation to be performed is given. Using stacks can be considered different from programming languages that resemble natural human language (e.g. {{w|COBOL}}). While stack-based computing makes some problems very simple (for example, it is relatively simple to design a Forth compiler, or reversing the order of an array) and uses less computing resources, such programming languages are not easy to learn. Since Forth allows the programmer to rewrite the language, or define their own language, and it does not enforce restrictions like data types, it may be especially easy for novices to write cryptic code.

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)