mastodon 4.7.3go slowly and quietly, and look deep
i've always admired and sometimes envied people who can think very quickly, in front of others. it's taken me a long time to appreciate slow and solitary thinking (which i relate to more naturally) as a complementary skill, but i hope i can do some good in the world by talking about it. if you process things slowly, you're probably noticing a lot more detail, taking less for granted. sharing what you learn, even at long delay, is a gift you may give others patient enough to deserve it
if i don't know how to elaborate your proofs to a logic whose definition i can fit in my head, i don't trust your proofs 🤷🏻
used to be "make a little logo for your project for a token amount of extra credit" was a way to give students permission to do a tiny bit of low effort art as a treat. everyone knew it could just be bad and that would be part of the charm; it would still connect you in a personal way to your creative efforts. i forgot this doesn't work anymore, and i'm sad about it.
re: examples (@chrisamaphone@hci.social)
when i meet a new-to-me logic or type theory, it's like someone has just handed me a phrasebook for a language i don't yet speak. the beauty of it is it gives me a new vocabulary in which to ask questions. example: when meeting linear logic, one can ask, "is [A & B ⊸ A ⊗ B] a theorem?" & the theory can answer. i eventually want to study properties of the theory from outside, but i build all my intuition from conversing with the theory in its own language.
💭 i should use "congratulations or sorry that happened" to illustrate the difference between internal and external choice in linear logic
listening to the album hours before the live show like i'm cramming for a final exam
a cool trick i once learned is that you can often decipher the pragmatics of corporatespeak (and academic adminspeak) by negating its semantics
unboxes your turtle
my favorite epistolary novel is the poplmark challenge mailing list archive
does anyone (i'm mostly looking at @pigworker@types.pl) have an implementation in runnable code for translating a strictly-positive inductive datatype to a container, i.e. the computational content of the attached corollary from "constructing strictly positive types"?
60 °F and windy in April is the coldest temperature, in the same sense that San Francisco summers are the coldest winters and a V3 i can't climb is the hardest bouldering problem