Stories
Slash Boxes
Comments

SoylentNews is people

posted by n1 on Friday July 14 2017, @02:40AM   Printer-friendly
from the I'll-second-that! dept.

Not one to let trivia pass unnoticed, the timing of this post has a mildly interesting significance.

Some of you may be old enough to recall the Y2K bug (or may have even helped in avoiding the predicted calamity). Thanks to an incredible effort, the world survived relatively unscathed.

So we're in the clear, now. Right?

Not quite. In the land of Unix timekeeping, there is another rollover bug coming up, when the number of seconds since the Unix Epoch (Jan 1, 1970) exceeds the space provided by a signed 32 bit number: 2147483647 (January 19, 2038 at 03:14:08 UTC). [See Wikipedia's Year 2038 problem entry for more details.]

The timing of this post marks our reaching 75% of that a milestone towards that rollover amount: 1,500,000,000 seconds since the Unix epoch which works out to 2017-07-14 02:40:00 UTC. (Queue Cue horns and fanfares.)

Besides taking note of a mildly interesting timestamp, I'd like to offer for discussion: Falsehoods programmers believe about time.

What memorable time (or date) bugs have you encountered?

I once worked at a company where the DBA (DataBase Analyst) insisted that all timestamps in the database be in Eastern Time. Yes, it would fluctuate when we entered/exited Daylight Saving Time. Even better, this was central database correlating inputs from PBXs (Private Branch Exchanges) across all four time zones in the US. No amount of discussion on my part could convince him otherwise. I finally documented the situation like crazy and left it to reality to provide the final persuasion. Unfortunately, a defect in the design of their hardware manifested at a very inopportune time, and the company ended up folding.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Interesting) by FatPhil on Friday July 14 2017, @07:11AM (1 child)

    by FatPhil (863) <{pc-soylent} {at} {asdf.fi}> on Friday July 14 2017, @07:11AM (#539002) Homepage
    because they're waiting to be played at the appropriate time?

    Apropos of nothing, etymology online has this insight:

    queue (n.)
            late 15c., "band attached to a letter with seals dangling on the free end," from French queue "a tail," from Old French cue, coe "tail" (12c., also "penis"), from Latin coda (dialectal variant or alternative form of cauda) "tail," of unknown origin. Also in literal use in 16c. English, "tail of a beast," especially in heraldry. The Middle English metaphoric extension to "line of dancers" (c. 1500) led to extended sense of "line of people, etc." (1837). Also used 18c. in sense of "braid of hair hanging down behind" (first attested 1748).

    It's curious to see:
    a) the french frenched up their own former simple spelling "cue". Fuck french spellings. Noah was right, english spelling sucks, and it's largely the fault of french.
    b) reference to a penis, I wasn't expecting that (though I was familar with the hair definition, having a 40+cm queue myself)
    --
    Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves
    Starting Score:    1  point
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 2) by Osamabobama on Friday July 14 2017, @09:49PM

    by Osamabobama (5842) on Friday July 14 2017, @09:49PM (#539360)

    Do you wear horns in your queue?

    --
    Appended to the end of comments you post. Max: 120 chars.