katrielalex

Lead author on the deletion paper here. Thanks for the feedback! I agree it would be cool to talk about the Ent APIs some more; they have a lot of obvious and less-obvious benefits. (For example, we are only able to add deletion constraints to Ents as described in the paper because the Ent specification language is expressive enough to do it.)

That's ok, pgp is also terrible to use on the command line so we can complain about that.

Depends where in the UK! https://www.oxford.gov.uk/info/20074/recycling_advice/25/wha...

The real part of the conference is the bit in between the talks.

(Fun fact, the first conference I went to had like five coffee breaks per day, and I got a coffee at every break and complained to someone at dinner that there was too much coffee and not enough talking. They explained it to me quickly enough!)

We evolved dying of dystentery in our very recent history too.

You need the API key to be long enough to be unguessable. Otherwise, I could get free stuff by just guessing someone else's key.

This is significantly longer than what you need to avoid a collision. The idea of having a three-character key is just crazy.

https://www.beeminder.com/gmailzero will do this automatically for you. Together with https://www.followupthen.com/ it makes it pretty easy to keep Inbox Zero.

A lot of the points here are really quite out of date. (For example, defaultdict has been part of the stdlib since 2.5, and namedtuple since 2.6.)