Git vs. Microsoft Teams

GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.

Incentivized

Positive: The virtual workspace created for a work team within the same company, for the resemblance of information and communications in one place.Negative: The access for members of a non-profit organization who have external emails from the host but need the same access as an internal person since their volunteer work is part of the very core of the federation.

Incentivized

• Ability to create branches off current releases to modify code that can be tested in a separate environment.
• Each developer had their own local copy of branches so it minimizes mistakes being made.
• Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
• Conflicts are displayed nicely so that developers can resolve with ease.

Incentivized

• Virtual meetings - ease of set up and execution
• File sharing! We build channels for projects, and being able to invite only project members is huge!
• Peer-to-peer communications - being able to "ping" one of my colleagues, either text, video or call-only, on-demand, is what runs our business.

Incentivized

• There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master.
• Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this.
• Many different GUIs, many people (including myself) opt to just use the command-line.

Incentivized

• The feature of notifications in the mobile application could be improved. Sometimes notifications of different teams are not visible and are only visible when the application is opened.
• It uses lots of computational resources while running and thus, slows down the system sometimes.
• It allows a few channels per team. The number of channels could be increased for better productivity.

Incentivized

Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.

Incentivized

Microsoft Teams is included with our Office 365 subscription and we have no intention of migrating off of Office 365 and Microsoft products. Since Microsoft Teams is included for free with our Office 365 subscription, and since we enjoy all the features, benefits, and functionality, there is no question that our team will continue to use the product

Incentivized

Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.

Incentivized

User experience has been much better than the previous Skype for Business app. It has an easy-to-use interface with persistent chats. The search feature is very fast and useful. MS Teams has mostly focused on Collaboration and team building features which are very useful for organizational communications. Since Teams is accessible from multiple platforms like Laptop, Desktop, Mobile phones, etc it has been very convenient from a Mobility perspective.

Incentivized

Rare, but outages do happen

Incentivized

Sometimes about once a week I get a message that says "Sorry, there seems to be something wrong". But it goes away in a few minutes.

Incentivized

I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.

Incentivized

Using Microsoft Teams has resulted in much faster business communications with both co-workers and consultants. There has been little need for support with this software as the interface is very intuitive and the product is overall very well designed. We did encounter an issue with the built-in phone service, however, this was quickly resolved by the support team.

It's easy to set up and get going.

Incentivized

I find everything I need for my day-to-day work.

Incentivized

I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different.
The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy.
It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.

Incentivized

Our company and IT department previously used Skype for our communication needs. Skype was not dependable in my opinion, because it seems each time I used it during a call and/or a meeting, I and several other team members would get disconnected more than once. This caused a great interruption of our meeting, caused team members to have to ask others to repeat themselves and caused a general lack of interest in employee attendance during meetings.

Honestly, this tool is worth every penny. Yes, it's not free and you pay for the quality of services and the license. But the ROI and the benefits are all there. Also, the renewal, negotiation, and contract terms are all very well explained by our Microsoft account manager, and she's a charm.

It does not appear to have a limit to how many teams and employees we can have using it

Incentivized

I used Skype for Business to take calls, hold conferences, and provide remote assistance to users. Microsoft Teams, on the other hand, is superior to Skype for Business in my opinion. My job entails a lot of screen sharing.

• Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
• Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
• Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.

Incentivized

• I'm not sure I can point to a specific ROI, but it has improved our ability to communicate and work more effectively together.
• It's also nice to have records of every interaction, photo, and document that has been shared. Less chance of something completely disappearing.

Incentivized