Bharatvaj Hemanth
November 18, 2017
Recently I have made all projects of mine to use git and they are sitting on GitHub. The conversion process was painful but it was worth it. I was tired of maintaining all the projects manually and they were going nowhere. Because I work in different computers or in different Operating systems time to time and when I want to switch to another computer I had to copy the source code through a flash disc or ssh it to my other computer. Not only that, sometimes I accidentally work on older copies of my program. That's when I decided to add git to my work flow, from writing documents to programming. Writing documents in git sounds stupid but that's seriously helpful.
Of course, git has a learning curve. One needs to know the principles and commands and get familiar with it. But once it's done, it's done. Suddenly you can create code that is remotely accessible and you know that is the latest copy of the source code.
I even created a repository for my home folder. So rather than managing my *nix distribution every time I reinstall it or have to work in something like a college PC which takes me around ~1.30hrs just for setting up the work environment, I just git clone git@github.com:/../..git my home folder. And finally when I want to revert my college computer to it's former glory, I just git reset --hard.
If you are doing something that has anything to with change, git is always the best way to go. There is even a git library for C which also comes with a number of language bindings that makes it easier for developing software with git.