The Awesome Git
March 01, 2018

The Awesome Git

Christy Herron | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Git

I am a freelance, full-stack, software developer. Git repositories are used for all my code. I use multiple machines to create software for different platforms - Ubuntu to create websites to run on Heroku, and iOS apps. Git allows me to work on any machine while away from my normal setup. It also keeps all my source code backed-up, and I have the ability to grant access to my client if required.
  • Backup. It's the cheapest and easiest backup solution I've found in 20 years of coding. If/when a machine goes down I know I have no issues with losing work.
  • Access. I can access my code on any machine, anywhere I need to be. If I find myself with some spare time, and any machine at hand, I can dive in and carry on working.
  • Forking. It's very easy to fork new ideas without losing the current development thread.
  • I mainly use xCode and SublimeText, both of which provide a number of useful commands to backup my code to git. I'd like to see further integration, perhaps automated.
  • I couldn't do my job without git - I just couldn't got back to the old way of backing up and managing developers. I am now used to being mobile, having multiple machines, and zero concerns for hardware failure.
I've read about other solutions, but I haven't tried any as I decided that I don't need any features which they offer above Git . For instance, I usually just write my code in text files for languages such as Heroku and Java, so I don't need features which are IDE specific (other than xCode perhaps).
Developers often work in pairs, and on multiple projects at once. Sharing code across multiple machines can be very difficult. I don't know how we did it before Git came along - well, I do, but it wasn't pretty! Git has been a lifesaver on many occasions when systems have gone down due to hard drive failure. Git has also made it possible for me to manage and monitor the input of remote developers, as I can see in the commit logs for each push to the repositories.