I appreciate your perspective, Bill. Healthy discussions like this are what lead to positive change. Personally, I'm not tied to a clock - I've been self-employed for over 30 years and have always set my own schedule. So the time change doesn't affect me as much as someone who has to be at work at 9:00 a.m. every day. That said, my body is naturally programmed to wake up at 9:00 a.m., and thanks to the time change, I've been getting up at 10:00 instead. It'll readjust over time, but it's still an unnecessary disruption.

I completely agree that having more daylight after work is great. I'm all for leaving daylight saving time in effect year-round. In fact, I'd be fine if we moved the clocks forward two hours and just left them that way. My main gripe is with the constant switching. It's a hassle from a personal standpoint - having to go around changing clocks that aren't internet-connected - and from a programming perspective, which I've covered in several of my videos. Dealing with time zones and daylight saving time changes in software development is just an extra layer of complexity that serves no real purpose.

As for the health effects, I'm not a doctor and haven't conducted clinical research myself, so I can't say for certain. But I do know that time changes can have an impact. Living in Florida, I've traveled to both Hawaii and Greece, and jet lag is absolutely real. The first couple of days after arriving - and again after returning - are always an adjustment. Even an hour shift in the wrong direction can throw things off for a while, especially for people with strict routines.

And yes, I know I didn't technically "lose" an hour of sleep - it all balances out eventually. But for me, it's not about the missing hour. It's about the unnecessary disruption of having to adjust in the first place. If we just picked a time and stuck with it, there wouldn't be an issue at all. Your body would slowly acclimate to the changing amounts of sunlight as humans have been doing for hundreds of thousands of years - not jolted into the future/past by a modern invention.

Cue Back to the Future music...

Even the time back to standard time is worth it since it moves sunrise to an earlier hour providing school safety.
Jet Lag is real, but the move to Hawaii and Greece are far more than a one hour move.

From a programming perspective though you are 100% correct.  Use UTC and you're problems are solved.  There must be a way to display local time but store utc.  That would be helpful... but i do appreciate your opinion and your content.  I've learned quite a bit.

I think it would be easier and better, if school safety is your concern, to just change the hours that school starts and ends. It would be easier to publish a schedule saying, okay kids in January, we're going to be starting school at 9 am, and then in March, we're going to be starting school at 8 am than it is to change all of society just for the safety of schoolchildren at the bus stop. Wouldn't you agree?

that makes sense.  Schools are just one example though.

Time zones were conceived almost 150 years ago, for the emerging technology of railroads.  Maybe it is time for a change again for the emerging technology of global commerce.

What the railroads were experiencing, when towns set their clocks by the sun, is very analogous to what business is experiencing today - time is too localized for the current technology.