Hacker News new | ask | show | jobs
by rogeruiz 1021 days ago
If you're more familiar with VSCode, you could use it as your visual diff tool, https://vscode.one/diff-vscode/

But essentially I only ever care about two versions of my writing. The current version that has been edited, and the previous version that basis for the editing. This lets me not have to put things in version control and allows me to only ever really have two versions of something on my plate at any given moment.

If you are more comfortable in the Terminal, you could use a tool like `opendiff` as well which just shows you the lines that have changed. I normally only do this after I have had some rest in between the document revisions. But this view will produce a diff and also is good when you're unsure about certain sections.

I'll part on one last piece of advice which is that you should focus on the goal of what you're doing and pick up new things along the way. What works for me might not work for you exactly and you might have better ways of approach the same given problem. Don't sweat the details until you have enough of them in your tool belt. Good luck!