Is there a neat way to try out the TCR (Test & Commit or Revert) in Dr Racket?
TCR test && commit || revert is an alternative programming workflow similar to TDD. Run the tests after every change. If they pass, commit. If they fail, revert to the last passing state. As you'll see, this means that changes that don't work just poof disappear. Putting changes at risk creates a powerful incentive to make changes in teensy tiny steps.
The traditional way would involve a version control system, but for trying-it-out-purposes all that would be necessary is to alter the behaviour of Run to:
I watched the linked video. He never runs into the obvious failure mode of trying something, having it fail & revert due to a typo, and having to type it all over again instead of just fixing the typo. And at around the 16min mark he admits that he practiced running through it a few times before recording. Maybe he demonstrates what that’s like in Part 2 or 3?
