https://arxiv.org/pdf/2104.09945, very interesting paper on time as the process of turning the indefinite future into the definite past. Fits nicely with the Epochal Time Model, IMHO and makes me think about quite some stuff in computer science (e.g. table/stream duality and materialized views, Datomic transactions or Kafka compaction). :thinking_face:

https://www.youtube.com/watch?v=bKwzONOGLxs

Just encountered a perfect example of how not to design an API. I need to programmatically create an issue in Linear with a labeled URL and a screenshot. I have to make 5 requests: 1. Create an issue and get its ID 2. Create a "URL attachment" with a title and a URL using that issue ID 3. Create a signed URL for the screenshot 4. Upload the screenshot data to that URL 5. Create another "URL attachment" to associate that uploaded screenshot with the issue If I want to add another file attachment, that's another 3 requests. And it's also as slow as a slug. At least I don't have to make separate requests for issue summary and description.

Have I been living under a rock not knowing that Htop can show I/O stats out of the box?