The proper form of your analogy is that you want to chip away at your code, not at a runtime image. The REPL is the advantage here (in Smalltalk), not the fact that there is an image.
Interlisp did not work like that; editing took place on in-memory lists and the definitions would be serialized into files on request, which were sort of treated like mini databases. Image-based development was used a lot on Symbolics machines, there are advantages to it over always loading from flat text files.
The image just makes the lively computation persistent.
Do authors write books sequentially, first-chapter to last?
Is code used sequentially, only in the same order those procedures are defined in a text-file?
Does the text-file order of procedure definitions help us understand the call sequence?