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

It is well-suited for an organization with many team members who are scattered throughout different locations. It offers organization and clarity to projects, files, and tasks in one centralized location. It would be a bit of an overkill for a small organization where everyone is in the same location 5 days a week

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

• Makes communication and collaboration easier through Chat.
• Lets us personalize and humanize face-to-face interactions through Meetings.
• Helps me effectively plan out my day through Calendar.
• Enables us to safely store and access our information through OneDrive.
• Simplifies calls and voice communication.

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 calendar function can improve it's not 100% feature parody with outlook.
• Better search for documents and contact with AI
• offer the same security for document sharing as is available in outlook. Especially concerning PII and documents shared to "external" contacts.
• Contact is hidden away in "Calls" and needs to be better exposed like it use too.

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

If you have the full Microsoft Office suite, it works really well because it's integrated well within its ecosystem, but if not, it can be annoying because it tries to open a shared file in the web versions of the file equivalents. The web version is also a bit slow, and the login is very difficult to handle if you have multiple Microsoft or Outlook accounts.

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

The overall support provided by Microsoft for Microsoft Teams has been quite good but there is still some room for improvements. Microsoft needs to proactively work on fixing the open bugs in order to provide a seamless experience to the users. But over the service and experience provided by the Microsoft team have been quite satisfactory.

Incentivized

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

Microsoft Teams offers a much more integrated experience between their chat and video call function compared to Google Chat and Slack. Both other tools are much better for internal communications are they have simpler UI without other features. Whereas Microsoft Teams can be used for more critical conversations, particularly between external companies, and has been very useful in sales conversations which is what we chose it for when speaking to companies that work exclusively through Microsoft.

Incentivized

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

• Because our unit decided to go all in with Microsoft Products, the integration and flow of our communication and files are seamless.
• Microsoft Teams is very secure. Only those who are logged in with their university credentials can access the files we share and the events we host. Therefore, we don't have to worry about privacy and security for the virtual events we host.
• If our virtual events are open to the public, joiners outside the organization often struggle to join because Microsoft Teams is not the most familiar tool amongst the public.

Incentivized