• Dan (unregistered) in reply to State Your Name
    State Your Name:
    TRWTF is the ridiculous and confusing MM/DD/YYYY format. DD/MM/YYYY ok YYYY/MM/DD ok but MM/DD/YYYY? No no no!

    Actually, MM/DD/YYYY is the only correct way because it is how people actually say dates. Ask someone when Christmas is and see how many say December 25 vs. 25 December. Then people throw in the year last if it is necessary.

    Actually, only Americans say Month-Day. People in England tend to say 'the twenty-fifth of december'. Actually.

  • no (unregistered) in reply to Peter
    The sun, moon and five visible planets add up to 7.
    Five visible planets? I suspect that if you look straight down, you'll find a sixth planet that's remarkably visible.
    naa, its turtles all the way down...
  • (cs) in reply to Matt Westwood
    Matt Westwood:
    All the comments about the calendar being based on one Earth orbit around the sun... come on people this isn't rocket science.

    The Gregorian calendar is based on a solar, or equinocal, year so that with the periodic corrections, the equinoxes and solstices fall on approximately the same dates every year. Effectively the calendar is tied to seasons which are determined by axial tilt.

    Now an orbit of the Earth around the sun is called a sidereal year and it is slightly different. The changes aren't noticeable in a human lifetime but they mount up over centuries; hence the "lost" days when countries adopted the Gregorian calendar in favour of the Julian one.

    So on, say 20th April, the position of the Earth relative to the sun is increasingly different every year.

    The changes aren't noticeable in a human lifetime... or ever. It's not like there's a signpost out there that we fly by every 1.000001 years that says "you are here, the same place you were about a year ago".

    You obviously don't know shit about astronomy, fuckwit.

    Astronomy ain't nothin' to fuckwit.

  • Gibbon1 (unregistered) in reply to Jay
    I think the person who invented leap seconds should be locked up next to the guy who thinks he's a bottle of ketchup.

    I disagree, I think that they should let me spend 5 minutes alone with the guy, just me, him, and a cattle prod.

    \No Pants.

    Also, the guys the design RTC clocks that keep time in mm/dd/y + hh:mm:ss instead of seconds + ms since whenever, I'll kick you in the nads if we ever meet.

  • (cs)
    string LegalYear = (intMon + "/" + intDay + "/" + intYear); ... Convert.ToDateTime(LegalYear)
    Oh my, hard-coded locale setting.

    What an efficient way to break the code should it ever be ported elsewhere.

  • TheJonB (unregistered) in reply to Raplh
    Your Name:
    YYYY-MM-DD is the only one that sorts properly and that's why it's the standard (ISO 8601). Anyone who uses anything else is the kind of person who becomes a featured article here.
    Dates aren't FUCKING STRINGS!

    Some files on a shared folder on our network drive:

    April 2011.docx August 2011.docx December 2011.docx Feb 2011.docx January 2012.docx July 2011.docx June 2011.docx Mar 2011.docx May 2011.docx November 2011.docx October 2011.docx September 2011.docx

    Notice how nicely they sort! (NOT)

    That's as dumb as wondering why these files don't sort numerically:-

    one.doc two.doc three.doc cinq.doc funf.doc

    Captcha "Damnum" strangely appropriate.

  • greenlight (unregistered)

    TRWTF is that Microsoft had the exact same bug, and it brought down their whole cloud http://blogs.msdn.com/b/windowsazure/archive/2012/03/09/summary-of-windows-azure-service-disruption-on-feb-29th-2012.aspx

  • IceUck (unregistered)

    I'd say that date handling in general is hard (judging by the number of times developers screw it up).

    I've run into bugs where I tried to advance a date by adding some multiple of 24 hours, only to cross a PST/PDT boundary and have the resulting date end up being off by one hour.

    It gets worse if your software deals with dates that go back in history a significant amount. There have been adjustments to our calendar at various points in history that make it impossible to use that kind of math on Gregorian dates.

    You end up having to convert to Julian representation, make your calculations, and then convert back to Gregorian.

    ...and then there's trying to manage multiple (fluctuating) currencies in a financial system (GAAAAAK!)

  • anonymous (unregistered)

    TRWTF is how they managed to fuck up Convert.ToDateTime so that attempting to parse "2/29/1987" as a date crashes and burns instead of correcting it to 3/1/1987 like it's supposed to:

Leave a comment on “DATE_NOT_FOUND”

Log In or post as a guest

Replying to comment #:

« Return to Article