|
While a greenie, the following code was (accidentally) released into production:
Messagebox: Title "Oops"
Message: "Mikel Sucks as a programmer since this should never happen."
|
|
|
|
|
How many times did it actually get displayed?
|
|
|
|
|
HA! Good Question. The circumstances were such that it really should have never happened.
It was one of those "when a user clicks x and Venus is in retrograde" scenarios.
So to answer you question: Once
After that, I plugged the logic hole and put a "friendly" error in its place.
|
|
|
|
|
At least the dev was nice enough to let you know that worse was yet to come.
In my first year of writing code, I had put in a "temporary" dialog for myself which ended up getting released. The entire message was "Oops". That was useful, wasn't it... D'OH!!!!
I wasn't, now I am, then I won't be anymore.
|
|
|
|
|
Thats the same thing my teacher said c'mon, that message is very unprofessional and when feeding your children depends on that its doesn't sound like a joke 
|
|
|
|
|
The message you get from Acrobat Reader if you make a mistake in PDF creation is nearly this useful (it is "There was an error reading the document", if I remember right).
|
|
|
|
|
Some of the latest bad error messages we've seen here are
"An unknow error has occurred" (yep, with the spelling mistake)
Another From a M$ app logged this useful message to the windows event log
"The"
I think that's my favorite.
|
|
|
|
|
My favorite...
"Ironically, we experienced an error while attempting to send the error report."
The only other thing I could think of to say was 'Error report sent successfully', but I don't like to lie to the users 
"Reality is merely an illusion, albeit a very persistent one."
-Albert Einstein
|
|
|
|
|
Honesty suits you well  
(yes|no|maybe)*
|
|
|
|
|
That could qualify as the 'best' or 'favorite' error. Ya gotta have a sense of humor in this biz.
|
|
|
|
|
Spelling mistake should be "DUH" not "The" 
|
|
|
|
|
A nice joke I encountered on some website:
"*Pic of broken computer* Oh no! What did you do!? Just kidding... An error occurred while processing your request" and then something about lemurs[^] trying to fix the problem 
What was quite bad though, I was recently working on a company application. Many times stuff go wrong and the user doesn't even know because Exceptions are caught at some lower level and never passed to the UI (a horror in itself). But then I DID get an error... Or rather a message box with an error icon. The message itself was non-existant
It's an OO world.
public class Naerling : Lazy<Person>{}
|
|
|
|
|
"The file '' could not be refactored." No, I am not leaving out the file name... it really used empty quotes.
Somebody in an online forum wrote: INTJs never really joke. They make a point. The joke is just a gift wrapper.
|
|
|
|
|
GL_Terminator wrote: depuration
Very odd word to use, since it's meaning refers to being cleansed or purified. 
Chris Meech
I am Canadian. [heard in a local bar]
In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]
posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]
|
|
|
|
|
Perhaps they couldn't think of an appropriate word, so they used that one out of desperation.
Somebody in an online forum wrote: INTJs never really joke. They make a point. The joke is just a gift wrapper.
|
|
|
|
|
A bad synonym for the "garbage collection" phase of memory management perhaps?
|
|
|
|
|
I dunno. I got an error message from microsoft visual C++ (either 6 or 2003, can't remember) refeencing an internal file and line number, and requesting I report the error to "a graduate student". I thought that was pretty weak for a big-time commercial product.
Back in the day, I remember running strings(1) on the executable for Framemaker. Along the list of other error messages was this really terrific one; "Evacuate now, in our moment of triumph? I think you overestimate their chances." I can't imagine what horrible condition produces this message, but presumably there is a terrific kaboom right after.
|
|
|
|
|
For me it has to be while I was installing a microsoft product on win2k and witnessed the following error message:
The installation was halted because the following error occured: No Error.
I guess the installer got a bit confused.
|
|
|
|
|
That's cute. Reminds me of one from a cryptic UNIX GUI in the 1990s:
+----------------------+
| Error 0 |
+----------------------+
| |
| No error text for "" |
| |
+----------------------+
|
|
|
|
|
DEC's RT-11 OS (I'm showing my age) also had a text-based Help system. You typed: 'Help [Command Name]' at the command line, and you got a screen of text, usually with things like command line options. If [Command Name] was not recognised, you got back the single line: 'There is no Help for [Command Name]'. The programmer had a sense of humor. If you typed: 'Help Me', you got back: 'There is no Help for you'!
|
|
|
|
|
I remember that! They also had error number 69 - no path to partner in their RSX system. Early networking.
|
|
|
|
|
I prefer the old BIOS message "Keyboard not found. Press any key to continue"
|
|
|
|
|
Yes!
This happened on booting old IBM XTs. If I recall it said
Keyboard error
Press F1 to continue
Maybe it was some laid back engineer's sense of humour?
Why make life more difficult than it is?
|
|
|
|
|
This one actually makes sense, it makes sure you fixed the error (by plugging in a keyboard) before continuing.
|
|
|
|
|
MS-DOS also had a "Screen not found" error message, which no one ever saw because it was meant to be displayed on the screen
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
