Today I learnt that the Travis status site shows the build backlog, if any: https://www.traviscistatus.com/ (see also https://stackoverflow.com/questions/29567063/how-does-travis-ci-org-throttle-builds/34809448#34809448)
miniblog.
Related Posts
Today I learnt about "bypass charging", a phone feature where it can run directly off the mains without using the battery at all. No battery charging, less heat, less battery wear. Nifty.
Igalia's post on self-hosting CI runners is a masterclass in build engineering. It shows dealing with weird API constraints, but still finding good designs.
I also learnt that some CI systems use OCR on Apple's installers to automate!
Today I learnt that Racket *intentionally* doesn't have a traditional REPL workflow. The authors were concerned about students not understanding the state between the current session and the code on disk.
(Arguably Jupyter has some of these features now.)

