Yestercode. When writing C, C++ or other text-based languages, I often comment out the code I'm replacing or reworking and write the new stuff just above or bel

Yestercode. When writing C, C++ or other text-based languages, I often comment out the code I'm replacing or reworking and write the new stuff just above or below it. The old code is right there for reference. I've also found it useful to use github in the browser. When writing a feature for the 2nd or 3rd time because the previous wasn't good enough to merge to master, I'll pull up the commits from a previous effort. That readily shows the changes I made last time I tried to do this. Maybe it's odd to be looking at an old diff rather than either version of code but it can be helpful at times. Someone once told me that Simulink had a visual diff tool, but they were threatened by N.I. for infringing a patent so the feature spontaneously disappeared in one release without notice. (or maybe I have the companies reversed) It might be back by now.