To really discover what interactive, image-based CL development is about, my pointers:<p>- <a href="https://www.youtube.com/watch?v=jBBS4FeY7XM">https://www.youtube.com/watch?v=jBBS4FeY7XM</a> (5min) my demo to show how to resume execution of a long running program, from the stack frame right before the bug, after having fixed and recompiled the function, without quitting the debugger hence without stopping the program, thus without restarting everything from zero.<p>- <a href="https://www.youtube.com/watch?v=nsKx40ab9SY">https://www.youtube.com/watch?v=nsKx40ab9SY</a> (20min)showing what saving and restoring an image does, differences between SBCL and LispWorks.<p>- <a href="https://www.youtube.com/watch?v=1aboMZkNDCY">https://www.youtube.com/watch?v=1aboMZkNDCY</a> developing a 3D graphics software.<p>- <a href="https://mikelevins.github.io/posts/2020-12-18-repl-driven/" rel="nofollow noreferrer">https://mikelevins.github.io/posts/2020-12-18-repl-driven/</a><p>- debugging CL tools: <a href="https://lispcookbook.github.io/cl-cookbook/debugging.html" rel="nofollow noreferrer">https://lispcookbook.github.io/cl-cookbook/debugging.html</a><p>- and no: while we could deploy a ball of mud to production, we can also not and use traditional tools and techniques: build an executable from scratch, restart the app, reload state. But we can do everything in between too (inspect the running app, change it a bit, change it a whole lot (while staying in sync with local source code), use images to speed-up development etc).