GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It's that biannual insanity in the US where we have to change the non-internet-connected clocks. Worst is the coffee pot. Who still thinks this is a good idea?
My worst DST experience was missing a college test on Monday morning after going through all of Sunday without noticing the time change.
No stories. And yes we forgot time change down through the years for one reason or another.
As for me and people I work with, we want just one time used: standard or savings. Pick one. Don't care as long as we stick with it. As a programmer, it costs a lot of time to adjust for 23 hours and 25 hours for every process that is bean counter driven and for systems they do things on a 'timed' basis. Dealing across time zones is headache enough. Problem is not enough people have an 'issue' with the change ... so here we are.
It's that biannual insanity in the US where we have to change the non-internet-connected clocks. Worst is the coffee pot. Who still thinks this is a good idea?
My worst DST experience was missing a college test on Monday morning after going through all of Sunday without noticing the time change.
Anyone else have stories?
I agree, this twice per year stupidity is a terrible idea. Up here in Canada we're waiting for the US to make the switch to one year-round time. That'll be a great day when that happens.
No stories, but, even though I'm retired and I don't need to be anywhere at a particular time I find that this change leaves me feeling tired.
As for programming, everything was UTC so it didn't matter.
Unfortunately, data that is passed around for reports are not UTC. Even if they are you still have to show 23 hours one day, and 25 hours on the other in UTC time. Tough to get people to think in UTC time when looking at a report . But yes, UTC works at the low level for some things.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
. But yes, UTC works at the low level for some things.
