Fast feedback loops!<p>In my Fast Development workshop I recommend:<p>Goals are <i>speed</i> (low latency developer feedback), and <i>quality</i> (create something the client expects and values).<p>Speed: use `entr` or another tool to automatically run tests when a file changes.<p>Quality: "test" first -- write a test before code, if you have to think about the code. In this way you get high-level dev feedback, before the code is written.<p>Quality: use the system to calculate your function's result. Then either use "assert 0, value" to emit the result to you the developer, or use the debugger. In either case the computer does the work and you get feedback.<p>The above three-part process is similar to the OP, "conversational" is a good term for it.
We don't care about the REPL itself, rather that the language is 'image based' (see <a href="http://c2.com/wiki/remodel/?ImageBasedLanguage" rel="nofollow">http://c2.com/wiki/remodel/?ImageBasedLanguage</a>).<p>Also, very cool to see reference to Conjure on HN. That plugin is very impressive.
Could use an example of how this workflow is superior to having a debugger drop in repl like you can do in many languages. For example pry for ruby or debugger in chrome, which allow you to interact with the code in it’s current state. With lisp i think the benefit is you can evaluate as you go and skip debugging all together.