I've spent years of my life in career roles supporting international SaaS applications which involved scheduling, and it's been a grave disappointment to have been reminded on hundreds or even thousands of occasions that so many people are simply completely unable to wrap their brains around even the BASIC operation of the vexing monstrosity that is a "time zone."
Anyway, I fear it's probably best to leave this issue alone, as if the cries of frustration ever reach the madman occupying the office that used to be referred to as "Leader of the Free World," he's likely to issue an executive order which breaks everything which is currently limping along and leaves humanity in a wretched dead-end of never again being able to make any sense at all of "Trump Time."
It's not the time to talk about time. We don't have the time.
Obviously what we need js a computer vision system with GPS time to monitor the birthing process and register the time in an objective and consistent way. Not creepy at all.
What a timely post. Only a few days ago I was thinking about the limitations of a control system code which I have been developing. It uses Unix Epoch Time due to crash in a few years when the current 32 bit representation “rolls over”.
The solution is simple (I thought): we should just switch to a 64 bit representation and the problem won’t resurface for many billions of years! Just make sure everyone knows that any residual 32 bit hardware used for time-critical purposes must be e-waste recycled before 2038!
On a totally unrelated issue, I have just read a New Yorker article that I believe fits your interests. It’s about the likely use of bad science in a long accepted claim that Tylenol, its codeine additive in particular, was dangerous to the baby when given to the mother during nursing.
The struggle is real but for the industries I have programmed for, education and warehousing/distribution, I always get to say, "at least no one is going to die".
Most people don't care what time of day a student graduated. The shipping industry is a little more critical of time and some customers sure act like they are going to die when their package didn't arrive when we said it would!
I've spent years of my life in career roles supporting international SaaS applications which involved scheduling, and it's been a grave disappointment to have been reminded on hundreds or even thousands of occasions that so many people are simply completely unable to wrap their brains around even the BASIC operation of the vexing monstrosity that is a "time zone."
Anyway, I fear it's probably best to leave this issue alone, as if the cries of frustration ever reach the madman occupying the office that used to be referred to as "Leader of the Free World," he's likely to issue an executive order which breaks everything which is currently limping along and leaves humanity in a wretched dead-end of never again being able to make any sense at all of "Trump Time."
It's not the time to talk about time. We don't have the time.
Obviously what we need js a computer vision system with GPS time to monitor the birthing process and register the time in an objective and consistent way. Not creepy at all.
What a timely post. Only a few days ago I was thinking about the limitations of a control system code which I have been developing. It uses Unix Epoch Time due to crash in a few years when the current 32 bit representation “rolls over”.
The solution is simple (I thought): we should just switch to a 64 bit representation and the problem won’t resurface for many billions of years! Just make sure everyone knows that any residual 32 bit hardware used for time-critical purposes must be e-waste recycled before 2038!
Your post stirred me to find this article: https://en.wikipedia.org/wiki/Year_2038_problem#Solutions
I was, needless to say, COMPLETELY WRONG.
State by state, or county by county if you prefer, madness in the US sometimes. Here is Indiana.... https://www.ncsl.org/state-legislatures-news/details/navigating-two-time-zones-is-a-way-of-life-in-the-hoosier-state. I seem to recall Indianapolis did not have DST till it was mandated in 2006 but can't find any reference to that. My memory might be suspect.
My last comment should tell you that I just woke up (here in California).
On a totally unrelated issue, I have just read a New Yorker article that I believe fits your interests. It’s about the likely use of bad science in a long accepted claim that Tylenol, its codeine additive in particular, was dangerous to the baby when given to the mother during nursing.
https://www.newyorker.com/magazine/2026/02/02/did-a-celebrated-researcher-obscure-a-fatal-poisoning?utm_source=nl&utm_brand=tny&utm_mailing=TNY_SundayArchive_020126&utm_campaign=aud-dev&utm_medium=email&bxid=60d4a2b55f342c147b9be716&cndid=65485065&hasha=a31376b57d3bc5df6966d090fce37524&hashb=96018d9d18790d6453efba8af6e77c8bf1741633&hashc=6380806dd59ec8a6f779de9a070a6022765e88e2a29b7d7560906a9e10c970a5&esrc=&utm_term=TNY_SundayArchive
The struggle is real but for the industries I have programmed for, education and warehousing/distribution, I always get to say, "at least no one is going to die".
Most people don't care what time of day a student graduated. The shipping industry is a little more critical of time and some customers sure act like they are going to die when their package didn't arrive when we said it would!
GMT and a sextant will tell you when noon is.