miniblog.

One nice feature of cargo that I wasn't previously aware of: you don't need to do anything after updating your Cargo.toml. In npm, you need to remember to `npm i` after changing package.json. It's not declarative and the state can get out of sync.

I struggle with dependency syntax. I never remember what ^1.2.3 means or how it differs from ~1.2.3. I believe both npm and cargo assign the same meanings to this notation, but it's less obvious than e.g. 1.x. 1.2.3 isn't an exact version constraint either!

https://www.youtube.com/watch?v=0DLdQ6yb7h8 is a really accessible introduction to programming workflows with Sly for Common Lisp. The notion of 'stickers' is novel to me: you mark places in the code where you want to remember values (essentially tracing) or pop to a debugger (breakpoints).