Git it now! If you're working on a small or large team of developers, locally or remotely, you absolutely need to welcome Git to your team.
December 26, 2018

Git it now! If you're working on a small or large team of developers, locally or remotely, you absolutely need to welcome Git to your team.

Chris Martin | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Git

Git is being used throughout our organization by the majority of the development teams--custom app development and off-the-shelf customized products. We primarily use Git as a source-code management, a repository, and for revision control and deployment (integrated with other apps to support this function). Being on a large software development team with multiple different developers pitching in on in-house applications, it's essential that we have a tool like Git to manage multiple processes involved with app development. Git allows us to release development changes faster and minimizes potentially negative impacts to our production releases. I also use Git for personal hobby and freelance projects.
  • Git allows for collaborative development projects, without worrying about impacting the master revision. By using branches in Git, developers can get a messy as they want, knowing that they can revert to a previous revision.
  • The ability for co-located and remote teams to develop on a single project independently. From a business perspective, this allows you to strengthen your team by not limiting your employee or team selection processes to a specific geographical location. It also eliminates the requirement for a physical centralized location for co-workers to meet and work.
  • Git allows for code-comparison so that developers can see what changes they're merging together.
  • One of my biggest gripes with Git is the learning curve. Although I am now fairly seasoned, I vividly remember the struggle to learn the ins-and-outs of Git when I first started using it. It has come a long way since I first started using Git, so there are now a lot of fixes to age-old problems, as well as GUI interfaces and 3rd party integrations, eliminating a lot of the initial learning curve for newbies.
  • A major impact Git has had would be the ability to easily manage code from multiple developers in a single centralized repository. The time it takes to merge code from multiple developers has made significant impacts on our product release times.
Git is best suited for storing and managing source code in a local or remote repository. For example, myself and 5 other developer friends are working on a hobby app, but we all work full-time, busy lives, and have no clear deadline in mind to develop this app. Each of us can develop our portions of the app independently on our own time, remotely checking-in our source-code revisions to a centralized repository. As each of us pushes our code to the repository, we can begin to merge the code together into a single revision. Let's say Joe (made up friend name) decides to go a little wild and releases some really experimental code that causes the rest of the app to fail when put into production. Since we used Git, it's easy for us to revert back to a previous release, removing Joe's code changes and fixing the issues with the release.