What to do when a simple code edit will reset your project?

I do not know the technical details of what types of edits require a reset. In particular I don't know why adding a With requires a reset; I would expect it to be evaluated at runtime, and it should be able to deal with adding it below the current execution point.

However, if you are in development, then you should expect that to make code edits, you must re-run your tests. That isn't particularly painful--You just run the code again. It gets painful if you have a lot of user input that you have to repeat each time, but you haven't mentioned that (and there are ways around it). You can set a breakpoint at the spot where it stopped so you don't have to step line-by-line to that point on the next go-round.

This is the way it works. In all other programming languages I have used, not only do you have to stop execution to make a code edit, you also need to recompile and rebuild the project and run it again--VBA is the only language I've used that allows you to do hot edits. VBA is quicker when you change code because it is interpreted--you don't have to build it. Count your blessings.