TIL: You can intentionally add a (debug) function in your elisp code to cause a stack trace. If you do this, the variables and functions that are in-scope around that debug call will be available to eval! You can proceed to tweak and update things and double-check results before removing the debug.
Between stuff like this and live REPLS, Lisp did "intellisense" before it was cool.
@trevdev quite a few old languages had the code-debug-recode loop built in to their workflows like smalltalk. People seemed to get out of the habit with compiled languages...
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!