![]() As always, we’re indebted to the global community of curious coders who visit our site each day and participate in this survey each year. What are you waiting for? Go take the survey. We’ve continued to research alternatives, but so far have found no alternative that provides a cost effective alternative, considering the work we’ve already put in to configure Qualtrics. ![]() This is unfortunate, and we can do nothing about it. In addition, some users in China may have issues due to restrictions imposed by local internet service providers. To avoid issues that may prevent you from taking the survey, we ask that you specifically unblock Qualtrics in your plugins or pause the plugin while you take the survey.Īs in previous years, Qualtrics blocks certain countries from accessing their site and data: Cuba, Iran, North Korea, Syria, and the Crimea region of Ukraine (including Sevastopol). Our third-party survey partner, Qualtrics, doesn’t work very well with certain ad-blockers and security software. One thing to note: if you use a third-party ad-blocking plugin, you may see error messages during the pulse survey periods. We’ll be publishing the results throughout the year, so you can see the data even if you don’t see the survey. That doesn’t mean we’ll be bugging you for information every month these surveys will go out to a smaller subset of our users. To supplement our annual survey, we’ll be running smaller pulse surveys throughout the year on specific questions. We want to ask the right questions at the right time to better reflect the reality on the ground. While the annual survey will remain a touchstone, a yearly check in with the developer community, we’re making it smaller. ![]() Having learned how fast the ground beneath us can shift, we’re making some adjustments to our scope. And of those of you who search for an answer to your problem and find a purple link, well, half think warmly on meeting their old friend again. DevOps engineers make the most money on average. People who use Rust still love it, and it took the top spot for the fourth year in a row. We did manage to learn some things from last year’s survey. Those are the heart of any coder’s work, so tracking them tracks the evolution of the field itself. Of course, we’ll still include the old classics: things like favorite and least favorite languages. We’re asking about collaborating asynchronously and virtually, about managing projects and teams when all communication is remote. We want to see how coders’ lives have changed during this massive work-from-home experiment. So, what do we hope to learn with this year’s survey? For starters, we embark on this new research humbly, grateful for our community, and with a strong awareness that what is true today may not be equally valid in six months. Phrases like “unprecedented times” and “new normal” have become clichés. One year later, normalcy is creeping back in some parts of the world, but COVID-19 continues to be a daunting and immediate public health challenge for many regions as well. Anyone who kept their job was suddenly working remotely, and with that came a whole set of new process and workplace issues. The answers respondents gave weren’t irrelevant, certainly, but so much of what was in our survey no longer reflected people’s day-to-day reality. By the time the data was ready for release in May, the world had changed for most people. It was another chance to gather data for some of our classic, long-running questions, sprinkle in a few new ideas, and continue working to improve in areas like diversity and inclusion. Last year marked the 10th anniversary of our annual Developer Survey, and when we launched the questionnaire in February of 2020, we saw it as a milestone to continuity. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |