TypeScript Surge Flatlines in the new GitHub Octovere report – Visual Studio Magazine
TypeScript Surge Flatlines in new GitHub Octovere report
Last year’s sprawling GitHub Octovere report saw Microsoft’s TypeScript programming language reach # 4 in the popularity rankings – a notch above C # – after starting at # 10 in 2017.
This year, that surge has stabilized. In fact, the standings are remarkably similar, with the only change being that Shell and C swap places, now ranking 8th and 9th respectively. Here are the graphics of the new report 2021 and last year’s report:
Otherwise, this year’s report gathered data from millions of developers using the open source code repository and development platform and segmented them to explore writing code faster, building documentation, and building communities. sustainable.
Here are the GitHub summaries and links to those individual reports:
- Faster code writing and shipping: Teams and developers who use automation to write and deploy code perform 27% better in open source and 43% better at work. Additionally, we found that these groups also report higher levels of satisfaction.
- Knowledge flow through documentation: Developers see a 55% increase in productivity with good documentation. README files, issues, and thoughtful contribution guidelines all help create quality documentation. Companies can also adopt similar practices by creating strong internal documentation and communities of internal sources.
- Sustainable and welcoming communities: Teams that report high levels of trust are twice as likely to have a healthy collaborative culture in companies, and three times as likely in open source communities. Codes of conduct, contribution guidelines, the right first issues, and respectful dialogue in GitHub chats signal safety and build trust.
A finding of the ‘write code faster’ report shows a drastic change expected in working practices before and after the COVID-19 pandemic. Echoing many other similar findings, it shows that hybrid programs (working both at home and in the office on various schedules) are expected to become the norm (47.6% of respondents) while co-located approaches (in the office all or part-time) is expected to drop from 41 percent of respondents before the pandemic to just 10.7 percent after the pandemic. Employees working entirely remotely are expected to drop from 26.5% before the pandemic to 38.8% after the pandemic:
“Our approach to working remotely last year reflected a lack of familiarity,” the report says. “We are juggling competing needs in our personal lives and at work while trying to maintain the same levels of productivity before the pandemic. In 2021, we have started to move from simple compensation while hoping for a return to the old days. normality “to really transform our processes with the awareness of the needs of remote work.”
GitHub’s advice for working in the new normal?
âThink about your own team, where you work now and where you will work in the future. How can you support yourself and your teams? Are you using processes and tools to foster effective collaboration? Merging pull requests, deploying code through pipelines, and organizing work become especially important when part or all of our team is working remotely. (all or part of the time). Our open source colleagues have been doing this for years, so they can teach us a thing or two about shipping software to distributed teams. ”
Other highlights from this report and tips from GitHub on using this data include:
What the data shows: Good automation helps teams communicate better and more clearly, and research shows that better information flow is the key to better culture. Having better tools also helps developers feel empowered to do their jobs and feel fulfilled.
Use of data: Use these tables to identify one thing you can work on to improve your job! Pick something at the bottom (at the end of an arrow), then go back to see what has a significant effect. For more details on each build, head to the associated repository for the survey items we used.
What the data shows: Once large repositories start using Actions, teams merge almost 2x more pull requests per day than before (61% increase) and they merge 31% faster. In all open source repositories, using Actions increases the number of merged pull requests by 36% and reduces the merge time by 33%.
Use of data: Automation helps teams. Try to implement automation around your pull requests to improve your team’s productivity.
What the data shows: Authorization procedures, access restrictions, or information fragmentation can introduce friction that discourage developers from reusing code. However, developer performance on the job can increase by up to 87% when reusing other people’s code is easy and does not introduce friction. The benefits of frictionless code reuse are also striking for open source projects: projects see 2x performance compared to those with more friction, such as slow processes or multiple layers of approval.
Use of data: Identify sources of friction when you and your team reuse code from other teams and repositories. Are there any obstacles such as long access approvals, poor indexing, or undocumented dependencies? What can you simplify or influence others to streamline?
To look for
What the data shows: Developers are almost 60% more likely to feel equipped to do their job when they can easily find what they need. Plus, they can achieve an 11% increase in productivity simply by having an easy-to-search team repository – a finding also supported by previous research.
Use of data: Think about your team’s practices; Do they support easy indexing and cross-referencing to make information easier to find?
What the data shows: This year, pull requests are merged fastest at work, almost 2x faster than open source. We’re also seeing work pull requests merging 25% slower than last year. When we compare the previous two years, we can see signs that the pace of work is returning to pre-pandemic levels.
Use of data: Think about your own work. What did you notice about how quickly your team or community finished the job this year? If your own team’s merge time has changed, what has contributed to that?
For the â2021 State of the Octoversâ report, GitHub noted he had broadened his research approach. “By increasing telemetry to 4 million repositories with survey responses from over 40,000 developers, you can read predictive results and tips for improving productivity in addition to quantitative summaries of survey results.”