- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Yep. Nothing pretentious about the US, or that comment.
What "looks" or "sounds" right depends on what you're used to. If you represent dates by saying June 5th, then 06/05/2009 makes sense to you. If you're used to seeing 5th June, well then 05/06/2009 will look right to you.
CAPTCHA: There's no time like the "praesent"
Admin
Admin
TrueWTF is on second one that there is both finnish and sweadish even if only 5% of finnish people speaks sweadish...
Admin
Getting an error while displaying the error is not necessarily a WTF, although it'd be weird if it's in a windows dialog box. A web application I work on has a similar message, usually triggered on SQL server errors. The normal error screen will try to render a pretty box with a menu above - database access is needed to show the menu. So if an error occurs, a php define is set. If an error occurs when the define is already set, both sets of parameters are dumped and die() is called.
Admin
I thought Apple's were 100% bug free?
Admin
Umm, maybe it's funny because it looks, not like an error message, but like the "Word of the Day" is "There was a problem reading the XML". If it had left the "Word of the Day" text blank and popped up a clearly-identified error box with that message, I wouldn't have found it funny. And it's doubly funny because I think "Reading XML is generally a pain in the neck and XML is way over-used" is the sort of Word of the Day that I would be likely to post.
Of course, if you didn't find it funny the first time, any explanation of why it's funny usually kills any humor value it might have had. You see, OF COURSE the chicken crossed the road to get to the other side. It's funny because you expect the person to explain why the chicken wanted to cross the road, not just to repeat the obvious.
Admin
I like the fact that the high is 4 degrees, the low 2 degrees, and currently 5 degrees. WTF? Oh, wait, it's weather.
Admin
Right. Now sort the file by date. . .
Admin
Which is why I prefer the YYYY-MM-DD method, or YYYYMMDD. Sorting by date works great (sorts nicely), and with a 4 digit year, it's completely obvious of the format, betcause YYYY-DD-MM is nonsensical.
YYYY-MM-DD is also pretty universal globally - even governments tend to use that format.
Admin
Whereas I, in England, would say "It's the second of May." The difference in abbreviated formats comes from the difference in language. Because of the confusion, I've taken to writing dates as "2 May 2009" (using the 3-letter abbreviation for months of five or more letters). Anyone who knows any version of English will understand that. Anyone who doesn't know English is likely to have problems understand more than just the dates in what I'm writing.
Admin
Admin
Over here in the good ol' US of A we don't say silly things like "Fourth of July."
A new road construction project is just getting underway, so they posted a sign to inform people of the upcoming road closure. The sign read "Road Closed June 09 to Oct 2010" The sign was only 8 characters across, but still couldn't they have been consistent?
Admin
Admin
AND, by all means display an error message, but what's wrong with changing the look of the page to do that (ie getting rid of the 'word of the day'. A little more effort, perhaps, but a user can quite easily mis-interpret an error message among other totally normal looking messages.
If an error occurred, make it damn clear to the user that what they're seeing is not expected, don't add 'in line' error messages. If this means you have to load the data before rendering the page, or that you have to make the page refresh if an error occurred, so be it.
Admin
Agree, Y/M/D makes a lot more sense...you can sort dates of the form 20090128 nicely
That being said, at least D/M/Y has an order (from most granular to least), unlike M/D/Y which seems muddled. Of course, I doubt people in D/M/Y countries would use sec, min, hour for time...although without the sec part they sort of do (not in writing it down, but in saying it, eg "twenty past twelve", rather than "twelve twenty"
Question, though, in countries where they use M/D/Y are people more likely to say "March('s) 6th" than "6th of March"? (ie is this a linguistic thing more than anything else?)
Of course to open the can of worms fully, I'll quote a teacher I once had "...the Americans, who never learnt to speak English properly..."
Admin
ISO 8601 dates are only unambiguous in the context of ISO 8601. Without that or some other context, looking at the string "2009-10-11" I don't know which of two possible dates you mean.
Admin
I won't pretend to understand how the icon is displayed, but I must say I have seen similar (half-loaded) icons on mesg Boxes when my computer starts to play funny buggers. Admittedly, this is usually when processes are starting to hang, so it would be unlikely that another message box would (successfully) be displayed over the top, unless it came from another process, in which case it wouldn't refer to the hung one. I tend to agree, looks like Shenannigans to me....
Admin
Special formats for special purposes. If I have a list of data, I'll format the data in the way that makes the most sense -- in that case context would resolve the ambiguity since if I see 2008-01-03, followed by 2008-01-07, followed by 2008-03-05, it's natural to assume those dates are sequential unless explicitly told otherwise.
If I'm writing dates standing alone in text, I'll use the form that's most unambiguous on its own.
Admin
Oh, so because you say "May 2nd" and not "2nd May" then d/M/Y makes more sense than M/d/Y. I'll keep in mind that you are the absolutely authority on such things. I could make an equally pretentious sentence based on "May 2nd", so the whole argument about the latter being more pretentious is a crock.
Both formats make sense to people who use them. I think I'll go with those here who seem pro YYYY-MM-DD - It makes more sense than either of the other two because it can be ordered easily (that is, without having to tokenise a string).
Oh, and grow up you twat!!!
Admin
Der englischmann werdet "der Zweiter Mai" sagen. Der unterscheid von den Sprachen kommen....
etc....
Admin
Admin
Fresh vegetables are NOT going to still be edible by August 2009, so there is no ambiguity in the date format in this context.
captcha=facilisis: too easy!
Admin
That is so obviously a fake I'm surprised it got posted; they must be running out of actual good images to post.
QED
Admin
Is there anyone using 2009-10-11 to mean the 10th day of the 11th month? As far as I know, if the year comes first and it's hyphen separated, that's always an ISO 8601 date. It's about as ambiguous as assuming these dates are in the Gregorian calendar; i.e. not really.
Admin
Admin
Amen. There'd be no yellow to paint in the exclamation mark's pixels. Plus, why the irregular dark blue border if it was real?
Admin
The XML thing is not a WTF, but is actually point on.
Admin
Alex, I'm aware that you may not be using a Mac yourself, but at least spell the operating system's name right. I don't go around calling Windows “WinDowsVista.” It's “Mac OS X” or “OS X.” “OSX” just makes you look like you haven't done your research; which I suppose would be a correct conclusion.
Admin
It gets worse in the actual country. You have universities that have a college of economics in Finnish and across the street is the college of economics in Swedish and considering at almost everyone speaks english there is probably a college of economics in english a few block away.
Admin
Of course the last one is wrong. That's the trouble with you computer programmers. The user doesn't give a damn about the black magic of XML and doesn't understand what it is. The app should have told the user that is wasn't working in plain English and discreetly displayed/logged an error code for diagnostic purposes.
Admin
Hasn't anyone heard of CMYD? 5th June 2009 would be 2006-09-05. What's so hard to understand about that?
Admin
And obviously it should not display the error message as a "word of the day". Geez guys come on get a grip.
Admin
Admin
The real WTF for me was "okay, what the hell is 'wild rucola'?" About three seconds of Wikipedia later, "okay, why the hell it's in Italian 'rucola' when there's a perfectly usable Finnish term, 'sinappikaali'?" I mean, I could understand if you used Italian names for pasta or something, but unlike the art of cuisine, botany isn't a highly technical form of rocket science with clear and specific technical terms of foreign origin =)
Admin
Wow... this is the perfect date format.
Admin
Please tell me you're a fanboi; no one else should get this upset about something so stupid.
If you do not consider yourself a fanboi then you may want to do a careful self evaluation. I suggest this test: consider carefully how upset you would be if someone called your Mac an overpriced security risk. If the answer is not "not upset at all." Then you are probably a fanboi (given existing evidence). This is not to say that you should cease being a fanboi, but rather simply accept and embrace the reality.
Admin
Admin
When the dates are for humans I use the name of the month. When the dates are for computers I use yyyymmdd. That isn't hard is it ?
Yesterday I got a printout from the library stating when the DVDs I borrowed should be returned.
It listed the date of borrowing as "June 2, 2009", then below listed the return dates as "07/06/09". WTF. when the hell is that ?
Admin
In Danish one would say 1096 as one thousand six and ninety
Admin
I've witnessed the political wars of a programming group which produced several programs which could display an error reporting the error message. However, it did it right: the second error message actually contained the error message that couldn't be reported before.
What happened was, senior programmer D insisted upon writing his own fancy error dialog, because the standard X Windows error dialog ran too slowly and used too much memory[1]. Neophyte coder J saw the code, and thought words similar to, "Wow. This is horrible. I should save this code to post to the Daily WTF in about 10 years, when it finally exists." Sadly, as a neophyte coder, he didn't manage to accomplish that laudable goal. However, he did note a number of potential problems, and reported them in the next team meeting, in front of everyone, including the manager, and the visiting director.
Senior programmer D saw his career flash before his eyes. Every potential problem was, in fact, quite likely, in real world scenarios. And everyone who might possibly have any say in his promotions/demotions and pay changes was in the room to hear it. So he did what any old programmer in his position would do: he denied everything, and explained that the neophyte programmer just didn't know what he was talking about, because he was too inexperienced.
After the meeting, the manager asked J to add a fix. But D reviewed all of J's changes. How could J insert this fix without him realizing it?
The answer was exceptions - all of the problems in question raised distinct exceptions, which would never be caught. So, T put in a change to add a global exception handler. Since all of the exceptions other than the ones in the error handler were caught elsewhere, all of the caught errors were in the error handler.
Unfortunately for D's career, he reviewed the code, but did not understand its scope, nor did he run it. He perceived it to be another local exception handler, and thus he would need to demonstrate how that local part now handled less well. He accepted the change, and started to prepare his rigged demo.
All of the other coders now found that the program was much more stable than before; in fact, it was rock-solid, instead of crashing randomly once or twice a day. However, it presented a curious double error message about once or twice a day, with the first error (the one under the other) blank.
The manager was especially fond of the new behavior, and directed D to change the second error message to include 'while attempting to display an error message stating[2]'. D did what he felt any senior programmer would do. He modified the code to automatically dismiss the first error window before displaying the second. This caused the program to crash about a third of the time it attempted to programmaticly close an error window.
The manager was overjoyed at this response. He instructed senior programmer B to remove D's access to the revision control system, demoted D to junior programmer, cut his salary, and had J promoted to junior programmer, with a provisional code review side job (no salary increase.) Finally, he gave himself a bonus of half of D's pay cut.
Then he had J make the coding change he'd told D to make. J did a little extra, and determined the mapping between the error messages that would've displayed and the error messages it was displaying. They were mostly the same, but there were a couple which were different (but still basically 1-1 on the translation.) For example, the null pointer exception became an out of memory error.
The exception handling code was then locked at that revision, until a couple years later, when D quit. The manager then had senior programmer J rip all of the old error messages out and just use the system error messages.
For what it's worth, at the start, I was neophyte programmer T. By the end, I was neophyte sysadmin T.
[1] While it was probably true that X's error messages were excessively resource intensive, normally one fixes this by ideally submitting code changes to the reviewers of the X window system, or more realistically, replacing them with ones own leaner, more robust version. D chose the WTF route, and reused memory (hopefully) allocated elsewhere in the program to partially compensate for the fact he coded like a raving wombat, and so his error dialogs were more resource intensive than the system ones. And they didn't check any return values.
[2] The error messages for why it couldn't display the error message were usually the same as the original message. In the couple of cases that it wasn't, N didn't think the user would appreciate the difference - after all, he certainly didn't.
Admin
I agree completely. For example, ASR dates[1] work just fine: 1993-09-5741.
[1] I am so bloody looking forward to the end of this September...
Admin
Admin
Well, the following screenshot is not fake:
[image]Rumpus FTP client for Macintosh. Extremely bug-ridden and stupid piece of shit. It must have had all of two error check conditions in the entire source code.
The most spectacular bug of all -- and the developer implied that this is by design -- is that upload resume, doesn't. It simply wipes what's there already, and writes the resumed part in its place, effectively replacing one incomplete part of the file with another. He steadfastly refused to implement upload resume, but also refused to return a "Not implemented" error, so it just ate the file instead.
Filenames longer than 31 chars (the pre-OS X limit) were accepted and stored, but folder names were not, throwing up a useless error (see below). Changes to filenames that resulted in a new name > 31 chars were silently ignored. You could store a long filename, but not rename to one. A long name to long name rename also failed.
Any reported errors only came out as "550 Command failed for unknown reason"; fortunately the program implemented optional debug-level logging that included OS error codes. I ran the server permanently in debug-level logging so that I could read off OS error codes; the Mac knew what absurdities Rumpus was trying to commit, but Rumpus didn't get it.
Drawing a dialog like that was, sadly, a one-off.
Damn, am I glad to be rid of that program.
Screenshot from Other GUI oddities. A lot more variation than Error'd, too.
Admin
The "error displaying error" thing is clearly fake.
Admin
Days are fractions of a month. Months are fractions of a year. That's why dd/mm/yyyy makes MUCH more sense.
But what can you expect from people who can't use the metric system?
Admin