Hacker Newsnew | past | comments | ask | show | jobs | submit | gslin's commentslogin

https://en.wikipedia.org/wiki/Goodhart's_law

> Any observed statistical regularity will tend to collapse once pressure is placed upon it for control purposes.


Using timezone not UTC for a global service is a crime, especially mixed with daylight saving.

This is how they say Wall St is all using Anthropic without saying Wall St is all using Anthropic.

Regular price window around the world: https://www.worldtimebuddy.com/?qm=1&lid=5368361,5128581,316...


Yes, it overlaps well with the market open time. But I thought Claude was good with coding... Does this mean major trading agents write code using Claude to make trading decisions? Or Claude models are relatively better than other models in non-coding trading work?

"Claude" is their chat bot product, so a peer of ChatGPT and used for everything. It by default uses their "Claude Sonet" models. "Claude Code" is their code-writing client application, which uses "Claude Opus" models.

https://platform.claude.com/docs/en/about-claude/models/over...


The US trading day overlaps well with the US business day in general (and to a lesser extent, European demand).

There's only one country in the world.




The beginning of that article is slightly wrong: the compiler should compute N(N-1)/2 (and does), because the original code adds up all the numbers from 0 to N excluding N. The usual formulation in math includes the upper bound: the sum of integers from 1 to N, including N, is N(N+1)/2, so you have to replace N by (N-1) if you want a formula for the sum where the last number is N-1.


Couldn't the compiler optimise this still? Make two versions of the function, one with constant folding and one without. Then at runtime, check the value of the parameter and call the corresponding version.


Yes, a sufficiently smart compiler can always tell you’re doing a benchmark and delete it. It’s just unlikely.


Quote from the first paragraph:

> Today, we’re announcing Amazon Route 53 Accelerated recovery for managing public DNS records, a new Domain Name Service (DNS) business continuity feature that is designed to provide a 60-minute recovery time objective (RTO) during service disruptions in the US East (N. Virginia) AWS Region. This enhancement ensures that customers can continue making DNS changes and provisioning infrastructure even during regional outages, providing greater predictability and resilience for mission-critical applications.



I believe a report with timezone not using UTC is a crime.


An epoch fail?


I think it makes sense in this instance. Because this occurred in us-east-1, the vast majority of affected customers are US based. For most people, it's easier to do the timezone conversion from PT than UTC.


But us-east-1 is in Eastern Time, so if you aren't going to use UTC, why not use that?

I'm guessing PT was chosen because the people writing this report are in PT (where Amazon headquarters is).


us-east-1 is an exceptional Amazon region; it hosts many global services as well as services which are not yet available in other regions. Most AWS customers worldwide probably have an indirect dependency on us-east-1.


My guess is that PT was chosen to highlight the fact that this happened in the middle of the night for most of the responding ops folks.

(I don't know anything here, just spitballing why that choice would be made)


Their headquarters is in Seattle (Pacific Time.) But yeah, I hate time zones.


The password `TPL075526460603` is also mentioned in CVE-2022-37255[1].

[1]: https://nvd.nist.gov/vuln/detail/CVE-2022-37255



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: