Page 1 of 1
Year 2000
Posted: January 10th, 2019, 1:18 pm
by kiloran
We've all heard about the Year 2000 problem, when electronic systems might have failed without corrective intervention by software geeks.
So why has there been no publicity about the Year 2019 problem? 3 clocks in our house have failed since the turn of the year. And not flat batteries, they are either working intermittently (with a new battery) or completely dead.
If it was just one, that would be believable, but 3 in a few days? What's going on?
--kiloran
Re: Year 2000
Posted: January 10th, 2019, 1:32 pm
by Rhyd6
Blame it on Brexit or Trump, that seems to be the default position these days
R6
Re: Year 2000
Posted: January 10th, 2019, 1:34 pm
by AleisterCrowley
Have we had a coronal mass ejection recently ?!
Re: Year 2000
Posted: January 10th, 2019, 1:55 pm
by UncleIan
AleisterCrowley wrote:Have we had a coronal mass ejection recently ?!
Is that a euphemism?
Re: Year 2000
Posted: January 10th, 2019, 2:19 pm
by didds
meanwhile T2K was 19 years ago - but in another 19...
https://en.wikipedia.org/wiki/Year_2038_problemBest hope everything is running on 64 bit (or greater) by then...
didds
Re: Year 2000
Posted: January 10th, 2019, 2:26 pm
by brightncheerful
Blade Runner 1982.
Re: Year 2000
Posted: January 10th, 2019, 3:15 pm
by bungeejumper
brightncheerful wrote:Blade Runner 1982.
Like it.
BJ
Re: Year 2000
Posted: January 10th, 2019, 4:29 pm
by XFool
Isn't this (relatively) well known?
It's a GPS equivalent of the Millennium Bug.
https://spectracom.com/resources/blog/l ... -need-knowAlthough that should be from April 2019! Perhaps it was a coronal mass ejection, or just space weather.
Re: Year 2000
Posted: January 10th, 2019, 5:16 pm
by scotia
They just don't make things like they used to!
We still have operating a clock which was a wedding gift to Dad in 1939, and my cousin still has a clock operating which was bought on the morn of the day that Dad was born in 1912. Regrettably Dad expired at 95.
Re: Year 2000
Posted: January 10th, 2019, 6:20 pm
by jackdaww
===========================
re 2038 issue , ive put it in my diary .
but coming up to 80 (this saturday) , it may not affect me.
Re: Year 2000
Posted: January 10th, 2019, 8:42 pm
by monabri
jackdaww wrote:but coming up to 80 (this saturday) , it may not affect me.
THAT'S a surprise.......
I thought it was Sunday!
Re: Year 2000
Posted: January 14th, 2019, 11:26 pm
by Clariman
When I started out as a graduate trainee programmer in 1981 I remember pointing out to the Project Manager and Lead Programmer that these programs wouldn't work in 2000. They laughed at me saying, "Don't worry about that - no-one will be using this software in 2000!" Who was laughing in 2000
Re: Year 2000
Posted: January 15th, 2019, 7:33 am
by jackdaww
Clariman wrote:When I started out as a graduate trainee programmer in 1981 I remember pointing out to the Project Manager and Lead Programmer that these programs wouldn't work in 2000. They laughed at me saying, "Don't worry about that - no-one will be using this software in 2000!" Who was laughing in 2000
==============================
but there was plenty of (well paid) work for us programmers in 1999.
most company managers just didnt prepare for a known event being due .
bit like brexit then ...
Re: Year 2000
Posted: January 15th, 2019, 9:36 am
by StepOne
Clariman wrote:When I started out as a graduate trainee programmer in 1981 I remember pointing out to the Project Manager and Lead Programmer that these programs wouldn't work in 2000. They laughed at me saying, "Don't worry about that - no-one will be using this software in 2000!" Who was laughing in 2000
Project Managers and Lead Programmers for a start.
Re: Year 2000
Posted: January 15th, 2019, 5:02 pm
by jdlemon
During the 1970s and into the 1980s we used to say that software had a lifetime of 5 years - at least that's what we said for accounting purposes.
In 2006 I was doing a Y2K migration which had some embedded software I'd written in about 1974 - so I didn't find it hard to change. The main software system was only about 20 years old...
Jon