Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Slack’s Incident on 2-22-22. Parent comment
Yes, which makes reasonable the complaint about mm-dd-yyy.
> So although there is ambiguity, it’s easily resolved by picking that as the default mentally and only back tracking on failure.
This is both more work and also error prone in the general case (although it works out fine in this case).
> Now in the more general case, this whole thing feels like a lieutenant/leftenant situation.
Not at all. Whether I read "lieutenant" or "leftenant", I know what you're talking about. If I read 2-10-23, I might miss your birthday party.
There are no comments on this comment yet.
Yes, which makes reasonable the complaint about mm-dd-yyy.
> So although there is ambiguity, it’s easily resolved by picking that as the default mentally and only back tracking on failure.
This is both more work and also error prone in the general case (although it works out fine in this case).
> Now in the more general case, this whole thing feels like a lieutenant/leftenant situation.
Not at all. Whether I read "lieutenant" or "leftenant", I know what you're talking about. If I read 2-10-23, I might miss your birthday party.