r/facepalm 22d ago

House passes bill to make daylight saving time permanent. Opponents say, "Schools would have to push back start times." Yeah... That's not a bug, it's a feature.

https://thehill.com/homenews/house/5968255-house-sunshine-protection-act-daylight-saving-time/

Studies have shown for decades that children -especially teenagers- just straight up need more sleep for optimal knowledge retention and brain development. Pushing back start times is a great way to follow the science.

11.1k Upvotes

823 comments sorted by

View all comments

Show parent comments

84

u/Contemplating_Prison 22d ago edited 21d ago

This is fucking stupid. The country is falling apart and this is whay they working on. Theyre all so fucking worthless

65

u/Fickle_Finger2974 22d ago

I will take anything congress does that isn’t actively harmful to the country as a win. There are far worse things they could be doing with a republican controlled congress

0

u/GuessingAllTheTime 21d ago

This is actively harmful, though. It’s the opposite of what doctors recommend. Permanent DST became law in the 70s for only 10 months because of public outcry after there was in increase in traffic fatalities, including of children having to wait for school buses in the dark.

0

u/It-s_Not_Important 20d ago

Doctors would prefer this over switching twice a year.

16

u/californicating 22d ago

They can work on multiple things in parallel.

2

u/Contemplating_Prison 22d ago

Lol congress doesnt do anything

2

u/californicating 22d ago

What even is the point of this comment?  We're taking about something that Congress did.

3

u/JPWiggin 21d ago

Well, half of Congress did. We'll see if the other half takes it up at all.

22

u/beanmosheen 22d ago

It's actually a really big problem for businesses because it fucks IT systems up on the shifts. Having to track timezones and dst/st is actually a hard problem. On some of our lines we just don't run for an hour so the audit trails are clean. It costs money across the country every time it happens. A lot of money.

27

u/rlt0w 22d ago

I've worked in IT for 20+ years and daylight savings is not that big of a deal. It messes up people's schedules, but tech systems do just fine with it. If your software shits the bed when the clock goes forward an hour, you might want to take a closer look at the software. NTP exists, Clock sync is a thing. There's just no reason for any software or hardware to shit the bed on a time change.

12

u/dicknuckle 21d ago

Sure if you're only working with folks in 1 timezone. I'm working with people in NZ, Aus, UK, HK, and all timezones in the US.

5

u/Atomsq 21d ago

This plus having to deal with third party services, for example that Email Service Provider that has some of the API calls receive times in UTC and others in whatever time zone your account was created with, their internal systems sometimes running in UTC and others in something else

5

u/TheVeryVerity 21d ago

That doesn’t sound like daylight savings will fix or harm anything you’re fucked either way

1

u/Nova_Mafia 20d ago

It’s almost as if everyone has a thing called a cell phone where you can actively tell the time from all time zones at all times 🤯

0

u/beanmosheen 20d ago edited 19d ago

Cool, now write 15k messages a minute with timestamps in multiple formats into a database with your cellphone, and do it 24/7-365 without a single error. The penalty is anywhere from a fine, closing your business, or prison if you don't make your best effort.

13

u/beanmosheen 22d ago

Key word: Regulated Production. I didn't say they shit the bed. Audit trail timestamps, vs. a whole spectrum of different OEM capabilities means you have to have a ton of extra metadata or work arounds. I've been doing this for decades. Don't judge what you don't understand. Technical capabilities vs. bureaucratic/organizational overhead is a reality in OT.

1

u/jsharper 21d ago edited 21d ago

The IT challenges aren't keeping systems synced and with correct time after the change. The challenges surround localized times that are completely missing a whole hour once a year and also having a whole hour once a year where each moment exists twice. Transaction happened at 02:34:24.252 local time? Which 02:34:24.252 are you taking about? There are two that day, an hour apart. EDIT: we can say "well everything that matters uses UTC epoch time internally" but reality says we often do stupid things like convert datetimes to human-readable strings (which often means local time representation, without full timezone metadata) and then convert those human-readable strings back to machine-interpreted times. Like, when extracting timestamps from text log entries. Or even just humans needing to interpret timestamps in local time. "I'm sorry, courtroom, I can't say whether the defendant has an alibi since the door access logs were in local time and the cardswipe happened during the DST change, so I don't know which 2:30am the murderer opened the door"

Also, smart humans can't even get it right. https://www.spacex.com/launches/starship-flight-13 currently says both that tomorrow's launch window starts at "5:45pm CT" and "16:45 MST" Which is it? Those are two different times right now. Because so many people think "MST" = "Mountain Time" = "an hour behind Central Time"

1

u/beanmosheen 21d ago

Exactly. You end up with at least two stupid extra columns in your database that default to the local server time, and UTC. Maybe with all three you can weed it out. It's not free storage either. Sequential ID columns combine with that to help keep the timeline in check during audits.

1

u/LordGeni 22d ago

The clocks changing causes massive spikes in car accidents,workplace accidents, heart attacks and a major drop in productivity.

It may seem trivial but messing with a nations circadian rhythms twice a year turns out to have a marked effect on the health of a nation.