Editing 583: CNR

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 10: Line 10:
 
"Could not reproduce" (CNR as per the title) is used here as a {{w|double entendre}}. Because the reported bug is that speech recognition failed on a young child's voice, the programmers attempt to reproduce (biologically) in order to have a child to use as a test subject to understand and fix the bug, starting by reproducing it (the bug). However the attempt fails, as shown by the negative pregnancy test, and therefore the bug report is closed with the reason being "could not reproduce": they could not reproduce the bug because they could not reproduce biologically.
 
"Could not reproduce" (CNR as per the title) is used here as a {{w|double entendre}}. Because the reported bug is that speech recognition failed on a young child's voice, the programmers attempt to reproduce (biologically) in order to have a child to use as a test subject to understand and fix the bug, starting by reproducing it (the bug). However the attempt fails, as shown by the negative pregnancy test, and therefore the bug report is closed with the reason being "could not reproduce": they could not reproduce the bug because they could not reproduce biologically.
  
βˆ’
Nowadays, developers of software usually have a centralized repository of bugs which generally uses one of a handful of standard interfaces for tracking problems and desired features in software.  There is usually a quick way of removing pending items from this system by changing the status to closed and selecting a reason from perhaps a dropdown list.  "Could not reproduce" is a standard reason provided in almost all of these systems, so the novel pun provides extra humor to software developers.  This reason also shows up in comic [[937: TornadoGuard]].
+
Nowadays, developers of software usually have a centralized repository of bugs which generally uses one of a handful of standard interfaces for tracking problems and desired featuers in software.  There is usually a quick way of removing pending items from this system by changing the status to closed and selecting a reason from perhaps a dropdown list.  "Could not reproduce" is a standard reason provided in almost all of these systems, so the novel pun provides extra humor to software developers.  This reason also shows up in comic [[937: TornadoGuard]].
  
 
The secondary joke is that Megan has chosen a ridiculous method of obtaining a child for the relatively simple task of testing the software. The obvious solution is to find a pre-existing child to use; {{Citation needed}} giving birth to (and, presumably, raising) a child would burden the programmers with serious expenses, health concerns, and responsibilities; and it would take years before the child would be able to speak clearly enough to use the program.  
 
The secondary joke is that Megan has chosen a ridiculous method of obtaining a child for the relatively simple task of testing the software. The obvious solution is to find a pre-existing child to use; {{Citation needed}} giving birth to (and, presumably, raising) a child would burden the programmers with serious expenses, health concerns, and responsibilities; and it would take years before the child would be able to speak clearly enough to use the program.  

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)