Thanks! Fabulous summary that makes it easy for me to reply even without giving a video views. Also some of us are neurally wired to have tabs of information steams coming and a video blocks that. Ahah.
Y2K is an interesting comparison. I remember everyone infecting the moment when it was no big deal. Meanwhile jurisdictions the world over are ditching it and that makes BC by no means alone or without examples to show it will be fine.
For me it was a quote I forgot the origin: why did we change time to match factory work hours when we could have changed factory work hours to match time. Answer is a tale as old as time.
Y2K was not a big deal because everyone worked really hard to mitigate the time issues prior to it rolling over. And people are doing that now too, so we provably won’t see too many issues.
The time zone thing is a big issue for devs because everyone’s time adjustments and databases have their own hodge podge of remidies for correcting time based on where you are. A friend has been working all year on software solutions and fixes in the industry.
Issues like prior sold airline tickets have a time you should be on the flight, which will now be different. And issues like some database has correct time adjustments with zones pulled from a central places while another database just has peoples hacks of plus an hour minus and hour tacked on.
Even iPhones were (and maybe still are) still shit at meeting timesa when you move through time zones.
Its a joke at work when people miss meetings, and we take bets on if it was their iPhone that screwed them over.
It would be nice if we all just used UTC regardless of what time that meant we starting our day.
.
Please, fewer video links. Or at least post the transcript. Not giving YouTube clicks when this could easily be an article.
Fair enough.
CTV suggesting end of daylight savings time is like Y2K all over again and people in BC are oh so confused about the whole thing.
Thanks! Fabulous summary that makes it easy for me to reply even without giving a video views. Also some of us are neurally wired to have tabs of information steams coming and a video blocks that. Ahah.
Y2K is an interesting comparison. I remember everyone infecting the moment when it was no big deal. Meanwhile jurisdictions the world over are ditching it and that makes BC by no means alone or without examples to show it will be fine.
For me it was a quote I forgot the origin: why did we change time to match factory work hours when we could have changed factory work hours to match time. Answer is a tale as old as time.
Y2K was not a big deal because everyone worked really hard to mitigate the time issues prior to it rolling over. And people are doing that now too, so we provably won’t see too many issues.
The time zone thing is a big issue for devs because everyone’s time adjustments and databases have their own hodge podge of remidies for correcting time based on where you are. A friend has been working all year on software solutions and fixes in the industry.
Issues like prior sold airline tickets have a time you should be on the flight, which will now be different. And issues like some database has correct time adjustments with zones pulled from a central places while another database just has peoples hacks of plus an hour minus and hour tacked on.
Even iPhones were (and maybe still are) still shit at meeting timesa when you move through time zones. Its a joke at work when people miss meetings, and we take bets on if it was their iPhone that screwed them over.
It would be nice if we all just used UTC regardless of what time that meant we starting our day. .