Version control is an affordable and yet powerful tool to travel back in time, to test out multiple concepts in parallel, to provide a safety net to identify the last version of source code where feature xyz still was functional (by bisection in commit history), … just to mention a few benefits to (re)consider. It already is helpful if you work on your own, and even more if you enter a collaboration. While initially designed for source code, it is extensible to anything «text like»* – including (because you mention it) LaTeX. See CTAN’s relevant entries in the topic cloud and support by dedicated editors like TeXStudio (for instance when writing a thesis).
Because you mention Windows as (principal) operating system accessible to you, possibly tortoisegit nesting into the pull-down entries of the Windows Explorer can serve you as point of entry for version control in general. By default, the setup runs in a way to be compatible to Linux/Unix and hence platforms like GitHub, GitLab, etc to ease future optional collaborations. The corresponding commands to the CLI may be learned one at a time (e.g., software carpentry, or learnxinyminutes).
(The analogue tortoisesvn for SVN/subversion requires contact to the «central server» for each checkout and commit. By today, I perceive this star-shaped design less flexible than the decentralized one used by git and hence moved most of my svn repositories to git.)
* If it comes to binaries (images in .png format, etc), the addition of git-lfs to git is more suitable.