miniblog.

One subtle behaviour of Claude that wasn't obvious to me: whilst each conversation is transient, permissions persist across conversations. So if you've given permission to run e.g. 'cargo test' or even 'cargo run', you need to be sure that all future invocations are safe too. You can see the current permissions with /permissions.

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.)

One day I am going to reach the height of technological sophistication, and every clock in my house will handle daylight savings automatically. I'm not there yet. I think modern appliances are getting better though. (Does a microwave really need to know the current time?)