I've heard the term 'mechanical sympathy' for the ability to write efficient code due to understanding how a CPU works.
Is there a legacy software equivalent? 'Architecture sympathy', where you've worked out the structure that the author intended and things begin to make sense?
miniblog.
Related Posts
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.)
My understanding of Rust Foundation and Rust Project has definitely improved following today's talk.
Rust Foundation: Handles financial, legal and bureaucratic stuff. Requires a supermajority of votes from both sponsors and the Rust Project.
Rust Project: Focuses on building.
Ooh, I've just discovered that you can enable actions on GitHub pull requests by default! This is the actions settings page.
My understanding is that GitHub introduced these limits to prevent people trying to run cryptominers on GitHub actions. Sounds like GitHub has largely fixed it.
