1722: Debugging
| Debugging |
 Title text: When you Google an error message and it gets no results, you can be pretty sure you've found a clue to the location of Martin's sword. |
Explanation
|
This explanation may be incomplete or incorrect: Created by a BOT - Please change this comment when editing this page. If you can address this issue, please edit the page! Thanks. |
Transcript
|
|
This transcript is incomplete. Please help editing it! Thanks. |
add a comment! ⋅ add a topic (use sparingly)! ⋅ 
refresh comments!Discussion
Cueball is describing the familiar experience of hunting down bugs through convoluted steps. There's obviously a leap from debugging a computer issue to finding a fictional sword.
Sword of Martin the Warrior is a reference to [1] from the Redwall series of books. The sword has passed through the ownership of many characters in its time.
Anyone notice how small the sword is? ----
141.101.98.42 12:40, 19 August 2016 (UTC)--swampers
The keyboard problem could be the sword stuck (or hidden) in it. 141.101.98.15 11:12, 21 August 2016 (UTC)
Google'ing for an error message. 99% of the internet doesn't understand that concept. *sigh* --108.162.237.220 15:13, 21 August 2016 (UTC)
Seems like the issue was with the mouse, not the keyboard, after all. --108.162.221.29 03:01, 22 August 2016 (UTC)
Personally I find it even more irritating when googling an error message gives results... but those results are only for the source code of the program giving the error. Which invariably is not commented well enough to actually describe what the error code means, let alone potential ways to fix it. What do others think is the most irritating? No results, or source code results? 141.101.98.92 15:01, 22 August 2016 (UTC)
My dad used to call Sierra when their games crashed, and he'd give them the error code, and about half the time they went "Wow! Nobody's ever gotten that one before! What happened?!". Dad, fortunately, found this amusing. 108.162.237.134 04:25, 7 September 2016 (UTC)
