Some Lisps can be both interpreted and compiled, which allows some lovely workflows.
You can iteratively evaluate code snippets, and only compile when you're happy with your new feature! This takes the compiler out of the iteration cycle, so you get feedback sooner.
miniblog.
Related Posts
I certainly see the appeal of an LLM system with full context and tool use (OpenClaw), but the lethal trifecta puts me off deploying it.
I do like the idea of an agent with a heartbeat though. A bunch of nice cron-style workflows can be built on top.
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).
REPL driven development in Python, contrasting with TDD and Clojure workflows: