Overall Satisfaction with Git
We currently use Git to track all changes in our multiple websites and landing pages, along with internal scripting projects. Git addresses the issue of keeping track of the code we have created, and maintains security and redundancy between employees. In this way, we can be sure that no one person or one device has all the information we use daily to keep our systems and websites running.
- Git works quite well to keep a record of the code and the changes made on code for our websites and internal scripting.
- Git allows multiple developers to work on a single project with the checkout process.
- Git allows us to track who makes edits, when they were made, and how we can go back and fix any mistakes or bugs.
- Git is FAST!
- Git can be slow to learn, and much of it is done through the command line.
- Git is a single solution for a code repository, so if you are looking for larger scale backup or documentation, it might not be the right fit.
- The ability to have a backup of our code on remote machines allows us to ensure our time and capital investment in it's development is not in vain.
- Team collaboration with git can speed up development cycles immensely.
- Even for small projects, having the code available to different users for review or training, helps our developers get up to speed on projects quickly.
While my experience is limited on Microsoft Team Foundation Server, my understanding is that it works only for windows development work. This leaves out developers of alternative languages. Since git allows any code to be placed in it (you could even use it to back up plain text documents), this seems to be a good solution for most. Although, if you are using Microsoft development tools, Foundation server is probably the way to go.