Quote: "The programmers used some pretty interesting strategies to overcome not remembering how the original code worked: they'd excessively use undo/redo to f

Quote: "The programmers used some pretty interesting strategies to overcome not remembering how the original code worked: they'd excessively use undo/redo to flip back and forth between the current state and the original state of the code (other researchers have found that Java developers do this backtracking behavior too! A lot.), they'd copy and paste the code block prior to modifying it, or they'd screenshot the code to use as a reference! I also asked 9 other engineers if I could come sit behind them as they were coding. Oddly enough they agreed, and even seemed eager to have someone witness their coding frustrations. It revealed many small reasons why modifying code is tedious (e.g., it is easy to mistakenly swap two inputs and not realize it). They also taught me some more strategies, such as duplicating their entire code project before making a change so that they could compare the runtime behavior of the original version and the changed version. I again saw them screenshotting code and a few of them would make notes on paper prior to making changes." I am sorry, I don't use LABView, so this might be a noob question, but!: Can't you use a repository and just commit/checkout changes with different instances of LABView opened for each? This way you can compare that at the tip of your fingers multiple situations?