The DU Lounge
Related: Culture Forums, Support ForumsCan you believe that 2000 was 12 years ago?
That's a whole "person who can no longer order off the child's menu" ago.
onehandle
(51,122 posts)The Architect of Citizens United:
HopeHoops
(47,675 posts)There were really only two problems to look out for, but both were significant.
1) Software that sorted by the last two digits of the year would get the sort order all wrong. I fixed a few of those, mostly in code that was written in the 80's.
2) A lot of programmers didn't understand the leap year rule that every 4th century is STILL a leap year, unlike the rollover of the other three. The rule is:
if year modulo 400 is 0 then
is_leap_year
else if year modulo 100 is 0 then
not_leap_year
else if year modulo 4 is 0 then
is_leap_year
else
not_leap_year
The danger was programmers not being aware of the first condition and moving straight to the second. In all the searching, I never found a problem with any of the code I had to deal with (much of which I had written) on the modulo 400 problem and in general it was pretty much a non-event, soft of like all of the predicted "raptures" and the upcoming end of the world because of the Mayan calendar. It still meant a lot of 12+ hour days and my eyes wanting to escape my head from pouring over code.
And, for reference, If I created a file right now that's date-time specific, it would be "201209221148_FileName". I KNOW that will sort correctly until the year 10,000. I doubt any of those files will still be relevant by then (if humans still exist).
On Edit: If it's a sequence of files with the same name where date is important, that would be "FileName_201209221148".
JustABozoOnThisBus
(23,354 posts)... just in case.
Part of the evening was spent figuring out if the little battery backup box under a desk could power a coffee maker, important stuff like that.
There was no economic impact to the company - we didn't get paid for overtime.
HopeHoops
(47,675 posts)All three spike power usage that can not only damage the UPS, but also cause brown-outs on the entire unit.
And I never got paid overtime either - I was salaried (a good one, mind you), but a 60 hour week was typical and usually on the low side. I even worked at home (with a 9.6 kbps modem, might have been 2.4, don't remember). You don't go into IT for the money, the glory, or even the job satisfaction - it's because you're a masochist.