308 GitHub Testimonials

Industry
Company Size
15 per page
  • 15
Reset
  • “Tokopedia was growing so big that we needed to move from a monolith into a microservices model."

  • “GitHub, in terms of cost and performance, is head and shoulders above everything else.”

  • “We message GitHub if we run into a major issue, and when we ask for support, we get a very quick response. We occasionally need support, but when we do, we’ve been very satisfied with the experience.”

  • “That’s where I want to focus our team’s time. I don’t want to focus it on managing servers or anything else.”

  • "GitHub gives them better visibility and control of user permissions and access controls than their previous solution."

  • “We use GitHub as a community management system–kind of like a social network."

  • “Just by being open source and publicly visible on GitHub, we have developers who directly contact us with bugs.”

  • “We leverage quite a lot of community input to design the roadmap."

  • “GitHub became the platform to bring all these teams together.”

  • “Being able to see the code others have written—even if it’s poorly done—can help developers learn from each other and try new things. Using GitHub, we can send source code as a URL to less-experienced employees who can view it and get training as projects happen. Also, searching in GitHub …

  • “Until now, team members almost never reviewed code or provided feedback, but since the introduction of GitHub, people started using pull requests to provide code reviews. Recently, there’s been feedback coming in from other teams as well, so we’re seeing collaboration across departments—that almost never happened before.”

  • “We want to make sure Plaid engineers are happy and that their tools aren’t getting in their way.”

  • "When we told the team we'd be rolling out GitHub Enterprise we were met with insanely enthusiastic cheers."

  • “Before GitHub, you would have one system for your version control and another for project management. Trying to integrate between them could be difficult."

  • “During the process, we’re available for any issues or questions. We want to ensure the team is only publishing source code that everyone is behind—open source is about discovering what you need but also giving something back.”