I tried to track changes to my notes a couple of times. But I didn’t find it to be useful, apart from having a backup during app testing
The thing is, that there’s so much to change all the time (revising, adding new staff, reorganizing what’s there…) that peeking at the history wasn’t giving me any insights. I had a manual revision tracking, too, where I duplicated notes instead of editing them, but that produced so much noise that I abandoned it.
In programming, working on a planned change and making it meaningful is not trivial, but possible. You set out to do X, and then you work on it until finished, and could make a “merge commit” from that in git to track one coherent change. – Imagine doing the same in your notes. That works if you only ever work on one topic. Once you e.g. need a month to process a paper, but also include new findings for totally different stuff on the side, keeping things clean would mean you’d need to rewrite and manually clean up and group the history. That’s extra work that could’ve gone into making the actual notes better, or capturing something else.
In short: Opportunity cost of maintaining a revision history is a thing. If all you do is take daily snapshots automatically, that could be a thing, but I doubt it’ll be interesting, because navigating years and years of changes and minor additions without a meaningful change message as your future self could be doomed to fail.