<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://www.explainxkcd.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=RJFJR</id>
		<title>explain xkcd - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://www.explainxkcd.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=RJFJR"/>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php/Special:Contributions/RJFJR"/>
		<updated>2026-05-01T01:55:52Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1833:_Code_Quality_3&amp;diff=139601</id>
		<title>1833: Code Quality 3</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1833:_Code_Quality_3&amp;diff=139601"/>
				<updated>2017-05-05T16:19:28Z</updated>
		
		<summary type="html">&lt;p&gt;RJFJR: +&amp;quot;The joke, revealed in the last panel, is that this is supposed to be a code review and Ponytail's feedback is useless for this purpose.&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1833&lt;br /&gt;
| date      = May 5, 2017&lt;br /&gt;
| title     = Code Quality 3&lt;br /&gt;
| image     = code_quality_3.png&lt;br /&gt;
| titletext = It's like a half-solved cryptogram where the solution is a piece of FORTH code written by someone who doesn't know FORTH.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|Please change this comment when editing this page. Do NOT delete this tag too soon.}}&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
A tactical light 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.&lt;br /&gt;
&lt;br /&gt;
{{w|Alan Turing}} was a British theoretical computer scientist, often considered the father of the field. His 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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
At the end of the final panel, Cueball, seeing that Ponytail is tired of reading his code, offers to ask someone else to read his code. Ponytail insults him again by saying that nobody would want to review his code after seeing it for the first time.&lt;br /&gt;
&lt;br /&gt;
The joke, revealed in the last panel, is that this is supposed to be a code review and Ponytail's feedback is useless for this purpose.&lt;br /&gt;
&lt;br /&gt;
{{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.&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[Ponytail sitting in front of a computer screen typing. Cueball speaks only off-panel, but since this is a direct continuation of comic 1513 and 1695: Code Quality and Code Quality 2 where Cueball is shown, there can be no doubt it is him.]&lt;br /&gt;
:Ponytail: Your code looks like song lyrics written using only the stuff that comes after the question mark in a URL.&lt;br /&gt;
:Cueball (off-panel): Sorry.&lt;br /&gt;
:[Zoom in on Ponytail's upper body.]&lt;br /&gt;
:Ponytail: It's like a JSON table of model numbers for flashlights with &amp;quot;tactical&amp;quot; in their names.&lt;br /&gt;
:[Zoom back out again. Ponytail has lifted her hands off the table.]&lt;br /&gt;
:Ponytail: Like you read Turing's 1936 paper on computing and a page of JavaScript example code and guessed at everything in between.&lt;br /&gt;
:[Zoom in again on Ponytail's face.]&lt;br /&gt;
:Ponytail: It's like a leet-speak translation of a manifesto by a survivalist cult leader who's for some reason obsessed with memory allocation.&lt;br /&gt;
:Cueball (off-panel): I can get someone else to review my code.&lt;br /&gt;
:Ponytail: Not more than once, I bet.&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Code Quality]]&lt;/div&gt;</summary>
		<author><name>RJFJR</name></author>	</entry>

	</feed>