• Some other, random Steve (unregistered) in reply to Steve (yes, the real Steve)

    A lot of us here in The Internet have been really worried that your spelling and grammar were not up to snuff, and that your internal documentation of this issue might not be as meticulous as we'd hoped. Thank you for putting our minds at ease.

  • james (unregistered) in reply to The Other Steve

    I cam across a similar issue in our systems about 2 months ago.

    Someone noticed that the production planner report stopped showing any 30day+ orders towards the end of last year. As we hit December, all orders due under 30 days started to vanish.

    As I dug into the five year old stored procedures behind the report, I found that the system used a reserved date of 25th dec 2010 for special orders. However that wasn't the best part. The production planner had a clause to ignore these special orders:

    WHERE order_date <> 2010

  • Ouch! (unregistered) in reply to ContraCorners
    ContraCorners:
    It's "reply". With the letter "p".
    True. But it's a simple typo of the kind we all sometimes make and notice too late to correct it.
    The period goes inside the quotation marks.
    Only in countries where the style guides have been developed by blind and insane typographers. Punctuation only goes inside the quotation marks if it's part of the quoted text.
  • (cs)

    Hmmm... I see you didn't account for the 14th period. Just wait till that one bites you.

  • (cs) in reply to Ouch!
    Ouch!:
    ContraCorners:
    The period goes inside the quotation marks.
    Only in countries where the style guides have been developed by blind and insane typographers. Punctuation only goes inside the quotation marks if it's part of the quoted text.

    Agreed. That's why, here in the USA, the period goes inside the quotation marks. Sigh.

    (There are, admittedly, a handful of us continuing to act as freedom fighters on this front. However, I'm holed up, and it's only a matter of time before they realize I'm outta guns.)

  • Genitus Prime (unregistered) in reply to Abrelt
    Abrelt:
    krupa:
    While he never got a direct answer to that question, Steve eventually found out through more that it everything seemed to be good right up until the end of December.

    There are other clunky sentences at the end, but this one just kills me.

    It is apparent that I need learn how to type properly.

    FTFY

  • Genitus Prime (unregistered) in reply to Mr.'; Drop Database --
    Mr.'; Drop Database --:
    Anonymous:
    Abrelt:
    It's the wlhoe ccnpoet taht the itranel odnirerg of wdors dsnoe't mttear as lnog as the bngeniig and end are crrcoet.
    Atlaulcy taht ccnpoet is dmtrnlbsoaey fsale. The whole concept breaks down as soon as words get to about 7 letters or above. Hence "dmtrnlbsoaey".
    I wtore an arhlitgom to rgnrareae leertts in a mneanr taht is pllarraitucy hrad to raed. It teirs to miismaxe the pudcrot of the lhistevneen dcnaiste bweeten the snligples and the lhtsineeven danciste beeetwn the pnatiircnuonos as mueersad by a maopnthee fcuointn.

    Source code, requires advas.

    FAIL! Your source code is readable.

  • Jay (unregistered) in reply to james
    james:
    I cam across a similar issue in our systems about 2 months ago.

    Someone noticed that the production planner report stopped showing any 30day+ orders towards the end of last year. As we hit December, all orders due under 30 days started to vanish.

    As I dug into the five year old stored procedures behind the report, I found that the system used a reserved date of 25th dec 2010 for special orders. However that wasn't the best part. The production planner had a clause to ignore these special orders:

    WHERE order_date <> 2010

    I can't help but wonder if this piece of code was not written in, say, 1990, and the programmer said to himself, "Let's pick a date way far in the future, like, oh, say 2010."

    We had a similar problem here: We have date ranges on sales tax rates, so when rates change, we can tell the system to use the old rate until such-and-such a date and then switch to the new rate. When they were entering all the tax rates that had no specific expiration date, somebody decided to put a far future date in: Jan 1, 2010. Guess what happened a month ago.

  • blunder (unregistered) in reply to Jay
    Jay:
    I can't help but wonder if this piece of code was not written in, say, 1990, and the programmer said to himself, "Let's pick a date way far in the future, like, oh, say 2010."

    It's not that at all. People in the past hated numbers that are divisible by 67.

  • return of blunder (unregistered) in reply to Jay
    Jay:
    somebody decided to put a far future date in: Jan 1, 2010. Guess what happened a month ago.

    That's because it wasn't far enough. They should have used Dec 22, 2012. It's a valid Gregorian date, but the History Channel tells me that there's absolutely no way that you would have to process orders on it.

Leave a comment on “Nobody Does Business on December 31st!”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article