The importance of source control (git, svn, mercurial etc etc) is not as keenly felt by a solo developer, but imagine doing what you do in a team of developers, all trying to SFTP their own copy of the code to a server. Unworkable.
Once you start using git, even on your own, you begin to see how useful it is. You commit small, well-named units of work, and you can see the history of what you wrote. Maybe you don't like a commit and you revert it. You can go back in time to any point. If you want to work on one feature in isolation, while having a stable branch that you can make hotfixes on, you can create a branch. This is very easy to do in git.
If you want to work in any sort of team, learning source control (especially git, as it is very commonplace these days) is vital – and it is extremely useful just on your own too.
Once you start using git, even on your own, you begin to see how useful it is. You commit small, well-named units of work, and you can see the history of what you wrote. Maybe you don't like a commit and you revert it. You can go back in time to any point. If you want to work on one feature in isolation, while having a stable branch that you can make hotfixes on, you can create a branch. This is very easy to do in git.
If you want to work in any sort of team, learning source control (especially git, as it is very commonplace these days) is vital – and it is extremely useful just on your own too.