Found the following section in info '(coreutils) date invocation':
29 Date input formats
*********************
First, a quote:
Our units of temporal measurement, from seconds on up to months,
are so complicated, asymmetrical and disjunctive so as to make
coherent mental reckoning in time all but impossible. Indeed, had
some tyrannical god contrived to enslave our minds to time, to make
it all but impossible for us to escape subjection to sodden
routines and unpleasant surprises, he could hardly have done better
than handing down our present system. It is like a set of
trapezoidal building blocks, with no vertical or horizontal
surfaces, like a language in which the simplest thought demands
ornate constructions, useless particles and lengthy
circumlocutions. Unlike the more successful patterns of language
and science, which enable us to face experience boldly or at least
level-headedly, our system of temporal calculation silently and
persistently encourages our terror of time.
... It is as though architects had to measure length in feet, width
in meters and height in ells; as though basic instruction manuals
demanded a knowledge of five different languages. It is no wonder
then that we often look into our own immediate past or future, last
Tuesday or a week from Sunday, with feelings of helpless confusion.
...
--Robert Grudin, ‘Time and the Art of Living’.
This section describes the textual date representations that GNU
programs accept. These are the strings you, as a user, can supply as
arguments to the various programs. The C interface (via the
‘parse_datetime’ function) is not described here.
* Menu:
* General date syntax:: Common rules
* Calendar date items:: ‘14 Nov 2022’
* Time of day items:: ‘9:02pm’
* Time zone items:: ‘UTC’, ‘-0700’, ‘+0900’, ...
* Combined date and time of day items:: ‘2022-11-14T21:02:42,000000-0500’
* Day of week items:: ‘Monday’ and others
* Relative items in date strings:: ‘next tuesday, 2 years ago’
* Pure numbers in date strings:: ‘20221114’, ‘2102’
* Seconds since the Epoch:: ‘@1668477762’
* Specifying time zone rules:: ‘TZ="America/New_York"’, ‘TZ="UTC0"’
* Authors of parse_datetime:: Bellovin, Eggert, Salz, Berets, et al.Kinda wish we had more user manuals with personality like this. Technical documentation need not be soulless!
packing for trips is actually way too hard. i always end up bringing things that i never end up using… but the cost of unused items is way smaller than leaving behind something i need, so it has to be this way.
i still think a class along these lines should be a General Institute Requirement:
zola (or other SSG)zola init, put together a website skeleton, and commit to gitzola serve and see how you can develop a static website locallyand the student would walk away with a barebones personal website
Discovered ghostty +boo. Very cute. Feel like I should celebrate Halloween
using this somehow.
i've forgotten how nice it is to have a metal ddr mat in the living room
I wonder if airport security thinks it's funny or annoying when I make faces at their recognition cameras.
I'm glad that I finally see someone else in math talking about what I described 3.5 years ago in my blog post Everything I need is on the ground. Saw the following passage in Kevin Buzzard's recent post on grief:
As a PhD student of Richard Taylor in the early 1990s, I quickly understood that the statement of the theorem which I would attempt to prove in my thesis relied on a construction of Deligne attaching Galois representations to modular forms. I suggested to Taylor that I first read Deligne’s proof before continuing, and he was quick to shoot down this idea, pointing out that my funding was for 3 years only and I simply did not have enough time to get on top of all of the relevant literature at this point in my career. I never did find the time to read Deligne’s construction, or the proof of the Langlands–Tunnell theorem which was crucial in Wiles’ work, or many of the other things which I needed in my thesis and subsequent work. So do I “understand” my own work? What exactly do we even mean by “human understanding of mathematics”?
This is in contrast to undergraduate (and olympiad) level math:
Of course we all know it means to understand undergraduate-level results; we have taught the courses and checked everything carefully. I am able to explain all of the undergraduate algebra courses which I have ever lectured, right down to the axioms of set theory and also right down to the axioms of type theory. I understand the material in a visceral way.
… Though if I'm being totally honest, there are still some gaps for me there. For example, I never did learn the proof of the eyelid claim used in IMO 2014/6; all I know is that it is not too difficult and it's written in the shortlist packet, but 12 years later I never got around to reading it.
Finally took the time to learn how to use bwrap for Claude Code
(see new box.sh in dotfiles).
It was actually easier than expected so now regretting not doing this before.
It finally dawned on me why camelCase is so-named. Took a while.
Woke up this morning to find that LAMV got a Chinese fan translation. Exciting!
Every time I hear people compare math with chess I die a little inside.
If only predicting the future was as easy as pointing to something vaguely-related and confidently asserting an analogy.
On a whim today I finally went and learned what the "Evan is Old" point is. Seems the name is five years old now?
Me: "Everyone's from South Dakota now".
Also me: StudentRegistration.objects.filter(country="USA").update(us_state="SD")
mfw when attempting to refactor my diary manages to trigger the OOM killer
Why I never get any work done:
ruff check passing locally but failing on GitHubI still feel a bit weird being described as an "educator" or "in education". Somehow it sounds too important. I'd rather just say I'm a teacher.
after refactoring my style file my diary no longer compiles and i kinda regret some of my life decisions
One of my few memories from elementary school
was writing a terminal game to play with myself in Python 2.
I didn't know time.sleep existed, so I had homebaked my own to the tune of
for _ in range(C * num_seconds):
passwith C worked out empirically. Back then I had two-space indents, and my editor was DrPython.
I kinda wish I could see the old programs just to laugh at it, but I don't know if I still have that ancient laptop.
It's kinda too bad RSA-260 is getting drowned out, so in case you haven't heard:
RSA-260 = 2211282552952966643528108525502623092761208950247001539441374831912882294140
2001986512729726569746599085900330031400051170742204560859276357953757185954
2988389587092292384910067030341246205457845664136645406842143612930176940208
46391065875914794251435144458199
RSA-260 = 4397328654844826923795068102505872571721883526553349659561256924505973939597
593482272505698004801207988043088656411102133523080581
× 5028695206842569864686141618253083416610081090075366674776775706538324961364
412200138116378509733307971876652984898985905923678379New handout: "Enough Python to solve $N = p^2+q^3$". Guest article by Andrew Lin meant for people working on the OTIS application.
https://web.evanchen.cc/handouts/C1Python/C1Python.pdf