Q&A: The 2022 Developer Survey results are here!

Posted on

You’ve waited patiently, but now the wait is over: the 2022 Developer Survey results are here. Over 73,000 developers from 180 countries each spent around 15 minutes answering our questions. This year’s survey was longer than previous years, as we wanted to keep track of new threads and provide a historical overview of the questions we ask from year to year. We are very grateful to you for the time you devoted to our investigation.

Our new questions were about how coders learn their craft. We found that older coders are more likely to learn from books, while the new generation of coders (under 18) rely on online documents and friends and family. The overall percentage of those learning to code online, however, has increased from 60% to 70%. With so many people working remotely post-pandemic – nearly 85% of organizations represented in this survey have remote workers – it could be that more and more of our daily lives are moving online as well.

Additionally, while the pandemic has pushed us out of the office and into working remotely, remote work can move us away from full-time employment toward more self-employed work. The percentage of professional developers who report being an independent contractor, freelancer or self-employed increased by about five points to 16.6%, while the percentage of those in our top five responding countries (US, India, Germany, United Kingdom and Canada) who have a full-time job a fallen. Has the shift to remote working also sparked a new wave of entrepreneurship?

Our other new line of investigation was version control. We previously included Git in the “Other Tools” section, where it took top honors. It’s no surprise that Git is by far the best version control system, especially among professionals, but what’s surprising is that 17% of learners don’t use a version control system at all. version. I guess they will wait to be integrated into their first job.

The great strengths of the developer survey have always been the tech rankings, where technologists profess their languages, frameworks, and more. the most used, loved, feared and sought after. The top five languages ​​for professional developers have not changed: JavaScript is still the most used and Rust is the most popular for a seventh year. The big surprise came in the category of most popular web frameworks. Showing how fast web technologies are changing, newcomer Phoenix took the most beloved spot from Svelte, itself a new entry last year.

Two years ago we asked you what you think about searching for an answer and finding a purple link. Spurred on by this, the team wanted to see how many of us visit the same question more than once. Our data experts have found that the majority of people keep coming back to an answer over and over again: 62% of regular Stack Overflow users view the same question multiple times over a three-month period.* One of our data scientists data tells us that he probably visits that question once a month. Why remember everything when you can use Stack Overflow as your second brain?

In this year’s survey, we had a special section at the end where we asked professional developers to tell us what impacts their productivity at work, how often it happens, and how long it takes out of their day. Over 36,000 developers responded. Their responses can help the developer community begin to quantify the impacts of everyday, unseen productivity friction.

In short, most professional developers experience some drop in productivity every week. 68% of respondents say they encounter a knowledge silo at least once a week. For people managers, often the most experienced developers, 73% say they encounter a knowledge silo at least once a week.

About 63% of all respondents spend more than 30 minutes a day looking for answers or solutions to problems, and 25% spend more than an hour a day. This impact on productivity can add up. For a team of 50 developers, the time spent looking for answers/solutions represents between 333 and 651 hours of wasted time per week for the whole team.

On the other side, 46% of all respondents spend more than 30 minutes a day answering questions. 32% of people managers spend more than an hour each day answering questions, while only 14% of freelance contributors spend more than an hour answering questions. Again, this impact on productivity can add up. For a team of 50 developers, the time spent answering questions represents between 278 and 568 hours of wasted time per week for the entire team.

Check out the full results of this year’s developer survey here. If you want to dig deeper into the data and come up with your own insights, we’ll release the results dataset later this year. And as we’ve been doing for a while now, we’ll continue to run smaller, targeted surveys on everything from web3 to what makes developers happy at work.

Our mission is to enable the world to build technology through collective knowledge. You all helped make this survey possible, and we hope the results give you some insight into where the world of software and technology is today. Please share the results of this survey and we’ll see you next year.

If you have any questions about the survey results, you can reach us at press@stackoverflow.com.

*activity from February 1 to April 30 of this year; “Regular users” are defined as those who visited Stack Overflow more than 5 times during the 3 month period – recurring users should emulate a typical employee who attempts to ask a colleague any question.

Tags: developer survey

Leave a Reply

Your email address will not be published.