A deep dive into Tokio's scheduler implementation, including exhaustively testing all possible state orderings with Loom! https://tokio.rs/blog/2019-10-scheduler/
Related Posts
Do any tech streamers try new software live? It'd be a really fun way of doing UX testing.
An ad hoc, informally-specified, bug-ridden, slow implementation of half of a text adventure game -- or as I like to call it, a compiler.
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.)
https://blog.racket-lang.org/2009/03/the-drscheme-repl-isnt-the-one-in-emacs.html