Viewing profile — akio

[dead]

Yes, they forecast thousands of U.S. elections and thousands of sports games, and their forecasts had excellent calibration—e.g., events they said would happen 30% of the time actu…

They went to the wrong place then. ---- Nov. 1, 2016 — Election Update: Yes, Donald Trump Has A Path To Victory — https://archive.is/kwdab > Tuesday was another pretty good day of …

Speak for yourself. That's not why I read FiveThirtyEight. The purpose of FiveThirtyEight was never to be an oracle for the average person. It was always a deliberately wonky site …

> FiveThirtyEight performed only slightly better than what you could find in any other reputable newspaper FiveThirtyEight gave Trump double the odds of the next highest reputable …

Trump's second-term clemencies so far have forgiven criminal debts of more than $1.5 billion. That's over 2,000x the amount amount eliminated by Biden's pardons ($680,000). These p…

If all your experience comes from Apollo Client and Apollo Server, as the author's does, then your opinion is more about Apollo than it is about GraphQL. You should be using Relay[…

> I think in this case Europe/Kyiv would actually change its UTC offset to match Europe/Moscow, which I'm pretty sure the TZ database would handle just fine. Another user has alrea…

> Appointments become past events. Sounds like an operational nightmare to convert all of them right as they become past events. That is fair. In some models there's a natural sepa…

We agree that you generally want some information that lets you resolve your event to an IANA time zone for calculations :)

Past events should just be stored as instants, not as a local time plus location or time zone. Further, I believe the historical data is meant to be handled by the named time zone,…

Evan Siroky's Timezone Boundary Builder[0] is a good source of time zone boundary mappings. It can be used via a library in nearly any language you would want[1], or loaded directl…

The events in question happen at a physical location at a local time, and so are stored as a local time plus longitude and latitude. If they were stored as instants, and then if a …

The consequences could look something like 50 shift workers showing up an hour late one day, or a user missing a critical meeting. Dealing with and debugging time zones is already …

A future appointment at a physical location is usually an agreement between two or more humans. Humans generally don’t use UTC for future physical events, nor they use a time in a …

That is not quite right. In Postgres, timestamptz (aka timestamp with time zone) represents an instant in time. timestamp (aka timestamp without time zone) represents what you are …

It is not as rare as you might think. The most recent time this happened was March of this year, with Chile's Aysén Region dropping DST and moving to the newly created America/Coyh…

Good point. As you mention, that doesn’t matter in this case, as even if a new named time zone is added, the stored named time zone would’ve been written before Europe/Dnipro was c…

You are wrong, and fauigerzigerk is correct. Future physical events, such as an appointment at a physical location, should be stored as unzoned time plus a location (such as an add…

No. Local time should nearly always be used to represent the time of future physical events (along side a geographical location, such as an address). Your method of using a named t…

The majority did not vote for Trump, and I question how many of the minority that did vote for him voted for this , specifically. Almost certainly not all of them, given his approv…

> So far as we have already formed engagements, let them be fulfilled with perfect good faith. A key part.

We use Infisical for both our dev and prod environments. If you're a YC company you can get your first year free. https://infisical.com

Chevron allowed massive regulatory changes whenever a new administration took over. At a time of high political polarization, no one should be asking that we defer to the whatever …

You can specify parts of a query should be sent in subsequent responses with the @defer directive, and your client and server libraries will handle the rest for you. Server side: h…