As a computer programmer and IT admin, ending Daylight Savings Time DST, could be worse than Y2K.

The changeover to DST was a few years ago moved to few weeks later in fall, and earlier in spring, and that caused some automated clocks to change over too soon, too late. But other than that we survived

sounds good to me, contract engineers will see booming business to fix a bunch of old code for companies

Let me guess: you are Gandalf over some legacy system in a dusty fortune 500 server space.

We'll be fine.

Yes I remember that, it did cause problems. And now there are probably 10x more devices. I foresee even more issues.

The real shit show will be when these corporations realize what an idiotic idea it was to use so many 3rd parties in China and India.

Alot of devices are programmed for DST being an option.

If some things fail it's not like they are all gonna crash. Most will probably just be off an hour.

ah the plan is to stop changing time back and forward every year and just leave it at daylight savings which is what it is set to now. So explain to me how this can be a problem. No more changing of the clocks means just that. Computers will no longer have to change the time forward and back and that means less intrusion on the operation of the machine.

Now we are letting this corrupt fucking government tell us what time it is.

Just like Y2K, no big deal.

Lol I made shitloads of money doing y2k impact analysis for PacBell and airtouch...let's do it again!

only windows user will suffer, linux is forever can exist outside of time even, no one needs to program it evolves itself

What?

And fu

Well you have until November of 2023 to figure it all out so get busy.

Fake... You don't call yourself an "IT Admin"

Wouldn't be surprised if it caused some trouble. Y2K Was NOT the nothingburger some people say. There was tremendous danger. In the mid 90s, I had a military colleague who worked on computer systems (satellites, etc), and there were TONS of systems that failed testing and had to be replaced. They kept that VERY quiet. The same thing was happening in the private sector too.

What Y2K was responsible for was the biggest upgrade in computer systems ever. A lot of Bill Clinton's economic success was because of the huge spending on computer systems in the mid to late 90s. It was real, but for some reason, the narrative was "hey, nothing happened!"

Yea, nothing happened because HUGE numbers of computers with upgraded chips were bought.

The DST thing, though? Hard to say.

Hahaha!
Cant believe people like you run networks. Then again, there are many small organizations that have IT staff that call themselves “Network Admin’s”.
You are straight up stupid.
Thats coming from a real Network Admin.

Timezones are just an addition or subtraction and updating the rulesets is not a big deal. Only if you have severely old and unsupported solutions education use non standard components would this be an issue.

dam, wow. this will be way worse than Y2K. Just AD alone, if clocks are off, there goes your DC's and Exchange. managing all this in 1 year or 2 is not long enough, no way. it should be a decade minimum.

From the NIST website:

The rules for DST changed in 2007 for the first time in more than 20 years.
[link to www.nist.gov (secure)]

As you can see, the date that DST starts and ends on has changed every once in a while by politicians whimsy. It's a well understood problem.

You might have a few embedded devices that this causes problems for, maybe even a security issue but I can't see this being a major concern.

most clocks and phones are programmed to change
to DST automatically. So now you have to manually
reset those devices. potentially could break OTP
and MFA logins that depend on accurate time. IOW,
you get locked out of your accounts.

in 2007, OTP and MFA were not in wide use.

I wrote a crypto currency in 2018. as a security
check, we require an ethereum-signed message with
a timestamp of + or - one minute of server time.

bing, your payment system quits working due to
time mismatch between systems.

.

there's literally options to turn automatic DST off, it's not a big deal whatsoever

For the programming I did we also had to take into consideration that not all areas even observe DST.

NTP doesn't even send DST information. As long as your devices are updating date and time from a server, OTP and MFA would continue just fine.

Doom always seems to be a year and a half away. Unless it's 2 weeks.