miniblog.

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

I like that most LLM UIs show your previous queries prominently. When figuring out where LLMs are useful in your workflow, it's nice to see what worked well (or not) in the past. Web search doesn't have this property. I rarely look at what I've previously googled.

I'm still figuring out where Copilot fits in my workflow, and I find it works really well *when I know exactly what code I want*. When I have e.g. two lines in mind, I can see if it will write them (saving me the typing), and it's trivial to validate correctness.