Log in

No account? Create an account
Oh no ... - Off in the distance
my journal
May 2016

The Bellinghman
Date: 2010-03-02 12:56
Subject: Oh no ...
Security: Public
The firm said that the fault had been caused by machines that had "recognised the year 2010 as a leap year".

Just how many incompetent programmers are there out there?

(I mean, I know there are different calendars in effect around the world, and that we'll only know whether the former Soviet Union is on the Gregorian or the Modified Julian system when we see whether they observe 2800 as a leap year. But I don't think anyone anywhere has every considered this year to have a 29th of February.)
Post A Comment | 17 Comments | | Link

The Bellinghman
User: bellinghman
Date: 2010-03-02 15:07 (UTC)
Subject: (no subject)
BCD is a pretty odd thing to find in something as new as this, though it's conceivable that a clock chip has a BCD year count output, and the code reading it assumed that it was outputting in hex.

A quick check with the calendar indicates that from Jan 1 to Feb 28, all the week days in 2010 and 2016 are actually the same - and it's only that 2016 has an intercalary day that causes the mess-up.
Reply | Parent | Thread | Link