305 GitHub Testimonials

Industry
Company Size
15 per page
  • 15
Reset
  • "When we told the team we'd be rolling out GitHub Enterprise we were met with insanely enthusiastic cheers."

  • “The ability to scale the system and respond to very large amounts of data is of utmost importance."

  • “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 had scaling problems, merge conflicts, and deployments were always an issue.”

  • “Usually a card will be connected to a pull request, so when the next step is a code review, that’s easy for someone to just click through the integration, review the pull request and approve it."

  • “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.”

  • “Students go from just loving video games but having zero knowledge of development to being full-fledged programmers."

  • “Our students spend their time building and debugging real applications.”

  • “Our philosophy is that if we teach them one object-oriented language in-depth, they can easily learn another one later."

  • "GitHub is the lingua franca of developers. The more you can make work feel native for a developer, the more positive their experience. Pushing both product development and our beta interaction onto GitHub was a happy experience."

  • “It's all about the person-to-person relationship. Technology is a key lever in enabling DVAG’s financial advisors to focus on this relationship.”

  • “They have one platform and UI where they can find everything—the source code, the workflows, the issues—all in one place and aren’t distracted by routine tasks.”

  • “It’s more efficient for the developers, because you eliminate the need to learn a whole new set of tools if you move from one project or team to another.”

  • “It’s an agreement that a piece of code is stable, that it’s passed a certain set of evaluations, and is ready to move from one location to another.”

  • “And it turned out it was saved in Kafka.”