2020 GitHub Education Classroom Report - GitHub Education
Skip to content 2020 GitHub Education Classroom Report Insights from the next generation of software developers Report Summary Technical education frequently evolves to serve new frameworks, languages, and workflows. As a service to the education community, every year we release the GitHub Education Classroom Report. This year, we surveyed around 7,000 students and over 100 educators to build upon our previous data collection from 2019 , 2018 , and 2017 .
This report has key insights into the student developer toolchain, how students are learning real-world workflows, and expectations around technical coursework. We offer this information to faculty looking to augment their instruction, or learn from the choices of other instructors. Tl;dr - Key Findings Pay attention to APAC and LATAM. The number of respondents from those areas rose from 2019-2020. The next generation of developers will know and use Python.
Adjust your stack, product development, and outreach accordingly. Browser-based tools are growing in popularity for small, discrete tasks. Younger developers will expect their potential workplaces to offer remote work (and use GitHub). Visual Studio Code is the number one choice of younger developers, for the second year in a row. For remote classrooms, faculty report struggling with student engagement and monitoring student progress.
At the same time we wanted to report insights that were more urgent and timely: how have teachers responded to remote classwork? How has their classroom practice changed, and how might we make tools to support this new context? We also expanded our area of inquiry to include the path to work: internship application patterns, rates of employment, and workplace expectations. While GitHub Education is not focused on recruiting, we are keenly interested in onboarding students to opportunity: we want to help students learn and earn.
Partners in our ecosystem, or those looking to hire young talent, can use these insights to connect with younger developers. It's worth noting that all of this data is self-reported. Further research would be required to compare reported usage and metrics against usage patterns. If you would like to use this data for our own research, you will find the anonymized data set at the GitHub Education repository under an MIT License .
Who we spoke to Around 1.13 million students belong to GitHub Education programs, and many elect to receive email updates from the team. Of those, 7,070 students and 165 faculty responded to our survey. We know that these individuals are students and faculty because when they “join” GitHub Education, we verify their academic status to offer key benefits. For students, those key benefits last two years. This survey reached out to students (and former students) who joined GitHub Education in 2014, 2015, 2016 and 2017.
We selected this segment to build upon our knowledge base from 2019 , and to learn more about the experience students have in transitioning from school to industry. Age of student (and former student) survey respondents Year joined GitHub Education 2014 2015 2016 2017 % of survey respondents 14.3% 16.1% 28.3% 41.3% Average Age 28.2 26.9 25.3 24.1 The gender of survey respondents, for both faculty and students, remained consistent from last year's report.
Gender of student and faculty respondents Female Male Non-binary Prefer to self-describe Students 8.3% 89.8% 1.3% 0.6% Teachers 6.8% 92.6% 0.7% 0% Racial identity of student and faculty respondents Students and faculty self-reported their race and ethnicity, with the ability to select multiple responses. Faculty self-report as predominantly white, and by a greater margin than previous data (71.5% in 2020 to 55.6% in 2019).
Since respondents joined GitHub Education anywhere from 3 to 6 years ago, it is not surprising that they are well along in their academic careers. Overall, 45.8% report earned a bachelor's degree, 20.3% report earned a master's degree, 6.6% earned a doctoral degree, and the remaining respondents responded with a variety of other educational attainments. Where the developers are In our 2019 report, 50% of student developers hailed from the United States, which dropped to 33% this year.
We saw more respondents from Canada (10% v. 1.9%) and India (9% v. 6.74%). While we can't explain the rise in Canadian respondents -- we hear Mona is big in Vancouver -- the growing developer population in the Asia Pacific region (APAC) has been documented. The Evans Developer Population and Demographic Study of 2019 pointed to APAC as being home to the youngest, and fastest-growing, developer population. APAC has the largest population of younger developers among the regions.
A little less than 3 million are under the age of 30, which is more than quadruple the number of developers under 30 in North America. 13% of respondents this year hail from Latin America, versus ~10% in 2019, which also matches Evans' projections: In 2019, Latin America's developer population is approximately 2.16 million, and it is projected to grow at an average rate of 3.6% over the next five years. Insight With developer populations growing at faster rates in APAC and LATAM, consider hiring developers remotely in these areas.
Hiring remotely is another way to introduce diversity into your workforce. What the developers use From our previous research into Git and GitHub adoption in the workplace, it's clear that the tools students learn to use in school often travel with them to work . Companies who make developer tools are eager to know what younger developers prefer, and how advancements--for example, in cloud computing, processing power, or connectivity--might affect their behavior.
One consistent finding, across the board, is the widespread adoption of Python and related tooling. In the past five years, many, if not most, of the top computer science programs in the United States have implemented Python as a primary language of instruction . Here at GitHub, we expect to see this trend continue: Python has applications across different domains, like data science, which makes it a suitable choice for instruction.
Faculty members who want to invest in tools that students can grow with will likely continue to choose Python and related tooling. Insight More students than ever will come out of school with Python as their first language. This is great news for organizations that leverage related tooling (such as TensorFlow) but may require retraining new hires if you have a different stack. The Developer Toolchain These early-career developers developers report using 2-3 tools as part of their workflow, including integrated development environments (IDEs).
IDEs exist to support the developer, to bring about efficiency and creativity as they write, refractor, or review. Visual Studio Code continues to be the number one choice among early-career developers, growing on the usage pattern from 2019. Here are a few of the larger trends in IDE usage from 2019-2020. Student preferences among IDEs in 2019 and 2020 Visual Studio Code IntelliJ PyCharm SublimeText 2019 52.5% 29.8% 19.8% 32.4% 2020 69.9% 49.9% 34.7% 28.0% * Students could choose more than one option, so percentages do not total 100% We've seen the wide adoption of editors that give developers superpowers--Visual Studio, IntelliJ and PyCharm among them.
While minimalist text editors like Notepad++ or Vim are unlikely to leave the developer toolbelt any time soon, more and more developers are looking to online editors to make quick changes. In fact, almost 40% of early-career developers we surveyed have used browser-based developer tools, such as repl.it, Codepen, and Code Sandbox. When asked about why they use browser-based tools, younger developers point towards ease of use and the low barrier to engage.
Some of the top benefits are: Speed. “If I need to quickly test something or prototype something, it's nice to have an easy, separate environment.” “Only for quick cod
The rest of this page is on the live site.