When I first started developing, I was doing the usual newbie stuff. I'd copy Xcode projects when I wanted to do a new version. Git seemed like a foreign language that was for teams and for me to download third-party libraries. I would make backups (zip files) all the time in case I needed to revert back to an earlier version. I knew this wasn't the proper way to do it, but as a solo developer, it actually worked enough where I was able to keep things straight. Every time I tried Git, I would mess it up and something wouldn't merge. I would either spend an hour or two trying to figure it out or just blow away Git and keep the branch I was currently working on. It was always frustrating.
That said, I'm now relatively proficient. Why? I took the time to understand how it works, when not to use Xcode, and finally persevered through the learning curve. I also committed to paying GitHub to host my private repositories. It means more when you are spending actual money. 😆 Check out this post if you need to update your Git game.
99% of the companies that can hire you will use Git and GitHub.
Follow these simple rules and you’ll become a Git and GitHub master by Ariel Camus