A magazine about writing software in Common Lisp and Emacs.
Most languages make you stop a program before you can change it. In Common Lisp you recompile a function while the program keeps running, and an error pauses the program to ask how to recover instead of killing it. This is what a working day looks like when nothing has to restart.
When a Common Lisp program signals an error, the stack is still there. Follow one bug from the signal to the restart you choose.
The commands you need on day one, the ones worth learning once they'd save you time, and the Sly tools to pick up after that.
For fifty years we've killed the process to fix a bug and called the wait part of the job. It never had to be.