Editing 1833: Code Quality 3
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== | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | This comic is a direct continuation of [[1513: Code Quality]] and [[1695: Code Quality 2]] in the [[:Category:Code Quality|Code Quality]] series, in which Ponytail continually insults Cueball's code style. In this comic, as in the previous, Cueball does not directly appear, only speaking off-panel; however, as it is a continuation of the series, it is clear that this is Cueball's code. | |
− | + | In the first panel, Ponytail references {{w|query string|query strings}}, which store information, such as search queries or page numbers, relevant to the URL. Query strings are not meant to be especially human-readable, so a song based on one would likely not be a good one{{Citation needed}}. | |
− | + | A tactical flashlight is a light that can be mounted on a gun for use in low-light scenarios. They tend to be very durable and very bright. Different models have different features and capabilities, so they are given cool-sounding model numbers. A JSON table of these model numbers would look like random data. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | {{w|Alan Turing}} was a British theoretical computer scientist, often considered the father of the field. His [https://www.cs.virginia.edu/~robins/Turing_Paper_1936.pdf 1936 paper] outlined Turing machines, a theoretical model for computing, as well as computability and the halting problem. Theoretical computer science is very different from practical coding; understanding the contents of the paper would not at all help a coder to understand today's algorithms, design patterns, and best practices. This is not helped by a page of | + | {{w|Alan Turing}} was a British theoretical computer scientist, often considered the father of the field. His [https://www.cs.virginia.edu/~robins/Turing_Paper_1936.pdf 1936 paper] outlined Turing machines, a theoretical model for computing, as well as computability and the halting problem. Theoretical computer science is very different from practical coding; understanding the contents of the paper would not at all help a coder to understand today's algorithms, design patterns, and best practices. This is not helped by a page of Javascript example code. {{w|Javascript}} is a popular programming language which makes web pages responsive to user inputs, and while Javascript arguably solves the problem in a practical manner (as opposed to Turing's very theoretical work), it does get a lot of criticism - for instance it is {{w|Strong and weak typing|nearly untyped}}, which allows the programmer to do very interesting things, like {{w|JSFuck}}. Then, example code is used to explain a concept in programming or demonstrate how a program works, but it does not actually run on any computer. "Guessing everything in between" would involve attempting to write code using skills that could range anywhere from the most basic programming to Turing's extremely advanced ideas. |
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 | + | 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. | + | {{w|Forth_(programming_language)#Programmer.27s_perspective|Forth}} is an old programming language that tends to be difficult to read. A {{w|cryptogram}} is a cipher puzzle, generally one easy enough to be solved manually. The title text implies that the code is so bad that it looks like unreadable FORTH code that is missing random characters. |
− | |||
− | A {{w|cryptogram}} is a cipher puzzle, generally one easy enough to be solved manually. The title text implies that the code is so bad that it looks like unreadable | ||
==Transcript== | ==Transcript== | ||
Line 42: | Line 29: | ||
:[Zoom in on Ponytail's upper body.] | :[Zoom in on Ponytail's upper body.] | ||
:Ponytail: It's like a JSON table of model numbers for flashlights with "tactical" in their names. | :Ponytail: It's like a JSON table of model numbers for flashlights with "tactical" in their names. | ||
− | :[Zoom back out again. Ponytail has lifted her hands off the table | + | :[Zoom back out again. Ponytail has lifted her hands off the table.] |
:Ponytail: Like you read Turing's 1936 paper on computing and a page of JavaScript example code and guessed at everything in between. | :Ponytail: Like you read Turing's 1936 paper on computing and a page of JavaScript example code and guessed at everything in between. | ||
:[Zoom in again on Ponytail's face.] | :[Zoom in again on Ponytail's face.] | ||
Line 52: | Line 39: | ||
[[Category:Code Quality]] | [[Category:Code Quality]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− |