From Gitalytics to GitHub Insights
At GitHub Satellite, the company previewed GitHub Insights, a product designed to provide development metrics. The product builds on work by the team from Gitalytics, a development analytics startup that joined GitHub a few months before the announcement. The two teams share a vision of advocating for developers and driving improvement through transparency, discussion, and collaboration.
What stood out after joining
The Gitalytics team says that joining GitHub meant suddenly working alongside the people behind tools they already knew well: the Primer design system, Bootstrap, and GitHub itself. More surprising was the broader talent across the company. New coworkers were strong communicators with deep technical experience who asked hard questions. As one teammate put it, "every interaction is a 10x learning experience."
The lesson the team draws from this: organizations are made up of people with distinct skills, and part of each person's job is to learn from and teach colleagues rather than concentrate knowledge. For leaders, that means actively encouraging knowledge sharing.
Adjusting to a distributed workforce
GitHub is nearly 70 percent remote workers, which was a significant change from Gitalytics' small, mostly co-located team. The shift to working from home changed communication practices. While stand-ups and real-time conversations still happen, the team now writes more and leans on asynchronous communication. That shift forces more transparency to keep everyone aligned on goals—though the team still misses working together in one room.
The takeaway: project success depends on more than code. Teams need goals that everyone understands and supports, and the medium and cadence used to communicate those goals matter, especially for distributed teams.
New constraints, new possibilities
At a startup, engineers often wear many hats. The Gitalytics team handled user research, sales, and marketing in addition to engineering. At GitHub, there is more room to think deeply about the product, serve both hyperscale and smaller engineering teams, and plan on longer horizons. The trade-off is that they sometimes trade speed for scale and resources, but they are able to approach problems more carefully.
The parallel for customers going through similar transformations: ambitious work takes focus and time, and tooling, culture, and investment should support teams in making the best decisions toward their goals.
A larger responsibility
The team is aware of GitHub's reach and influence, and that a product like Insights can shape how software is built for years. They see being at GitHub as a chance to build a product that can define, scale, and encourage best practices—and they view Insights as an early, evolving product they are determined to get right for developers, teams, and businesses.
Where GitHub Insights goes next
Metrics and analytics for software development remain a poorly defined and under-researched challenge. The team plans to continue working with the community and customers to evolve Insights, keeping it aligned with their values and vision. Like GitHub itself, Insights is intended to become a social, extensible platform that promotes collaboration and carefully researched best practices.
