Using SlashData custom questions to understand AI software developers

Our mission is to help our clients understand what the market looks like, what developers need, what excites developers, what doesn’t, and what they expect from our clients’ (and their competitors’) products and the developer programs that go along with them. So, when we are approached with a request for some custom work, we roll up our sleeves and dive deep into the data.

In this case study, we will be looking at how one of our clients, worked with us to understand the needs and preferences of software developers working with AI. 

The client is a company among the top 50 in the 2022 Fortune 500 ranking, which for the purposes of this case study we will be calling “Client”. This is the third installment in our “how we work with clients” series, and you can read part 2 and part 1 with Okta for more details. 

In this article, we will look into their request and more specifically:

  • The questions our Client wanted to answer
  • How we worked together on their problem
  • How they used the insights we offered them

The request

Understanding the needs of AI software developers

The Client wanted to better understand the needs of AI software developers, so we worked with them closely to understand the problem they were trying to solve. Then, together we made sure that we added custom questions to our Developer Nation survey, to get the answers from developers. 

Question: What was the goal/challenge you were looking to accomplish?

Client: We wanted to get feedback from our customers, who are software developers that work on AI, so we could get a better understanding of their needs:

  • What they’re actually doing 
  • The specific points that we are trying to optimize. 

We wanted to answer high-level questions such as what language they are using and high-level computing preferences. This is why we decided we want to have this survey. 

Q: Why did you choose SlashData?

At Client, we have had the experience of working with SlashData. And we did get a high value out of the previous report that you did for us. I was impressed by the support that I got when I needed it, the responsiveness, how you were always on schedule. The real part of working together. I felt how you put the customer at the front, the priority. All of these were very important to us. This is why we chose to work with you again on this project. 

Working together

I really got the feeling that you’re trying to understand real problems

Q: What did you like about the process of working with SlashData?

I really liked the execution: the ability to execute fast and answer our questions. We worked very well, very collaborative. Truth is, we did have a slow start. But then you said “let’s do this: you will write your assumptions, we will ask questions and approach this project this way”. Once we started that, work was progressing in a much better way. It was hard at the beginning, but I got excellent support. You had excellent questions, I really got the feeling that you’re trying to understand real problems. “What is it that we are trying to solve?”. You also asked questions to learn more about what we are doing, which I found very professional.

Q: What are the things you found challenging when working with SlashData?

We said that we would be adding X custom questions to your survey. But from our side, we tried to add more and more and we were left with all those very complex questions. 

Very complex questions are tougher to answer when you are looking to gain something specific. You did tell us to get the simple questions answered. This is what comes to mind in retrospect: Don’t make the questions too complex, trying to squeeze in more. You will get more value out of the simple questions, not the very complex ones. 

Deciding using the data

I used a significant part of those questions to presentations I gave to our senior executives.

Q: How did this project/report/data solve your problem/challenge overall? Did you understand the developers’ problems more based on the report?

I used a significant part of those questions to presentations I gave to our senior executives. I was especially more confident to use the less complex questions we asked. If I had my current experience in the beginning, I would have managed to secure a higher budget to ask more, simpler questions. 

data that show what our customers think and therefore, we could work with more than just our own thoughts and assumptions

Q: What decisions did you make using the data/research?

The work we did together was part of a huge project that Client is working on. I’m afraid I can’t disclose exactly the steps we did take after going through the analysis you gave us. What I can tell you is that senior management really liked the fact that we spoke to our customers and asked them directly. And not only that, but we also brought data that show what our customers think and therefore, we could work with more than just our own thoughts and assumptions. Client is planning for some huge products and of course there are a lot of parameters and a lot of things being done. But this data helped us pick a direction. 

How would you describe the service quality?

The service was excellent, really.

This interview is part 3 of the “How we work with our clients” series. The product this client worked with was custom questions and analysis and a custom report, to target their specific needs. You can also see how Okta managed to reach the top 3 in developer satisfaction using our Developer Program Benchmarking and how another client used our Deep Dives to boost their Developer Experience.

Working on a new initiative or want to make sure your product will win developers’ hearts? Talk to us. 

How do you measure the success of your developer-facing activities?

The Developer Program Leaders survey focuses on understanding “what makes a developer program successful” as viewed from the perspective of professionals in the field.

This survey brings you and the members of the DevRelX Community insights on how DevRel and Developer Marketing professionals:

  • Run their developer programs
  • Prioritise their work 
  • Segment their audience 
  • Measure success
  • Justify the value of their developer program to senior management and more!

If you are a DevRel, Developer Marketing, or Product Manager, your input is precious.

You may also think of it as an open-source initiative to better understand how the world understands the value of developer marketing and relations. 

In the survey, you will find questions such as:

What metrics do you use to measure the success and ROI of your developer program? Do you segment your audience?

These questions (and a few more) need your input. The latest wave of the Developer Program Leaders survey is now live. 

What you gain by responding:

  • Full access to the findings in an interactive session supported by SlashData’s research analysts, hosted within the DevRelX community
  • A chance to win exclusive DevRelX swag
  • You take part in a community effort to understand and improve how your peers work and set their strategy

How long is the survey? It is short. You’ll need ±8 minutes

Shape how the world understands the value of developer marketing and relations!  

Take this short survey.

The survey closes on November 14.

DevrelX Summit: Elevating the DevRel community, together

The DevRelX Summit is a community takeover, an opportunity for Developer Marketing and DevRel managers, strategists, practitioners, and enthusiasts to come together.

SlashData, which powers DevRelX and the community behind it, is organising a Developer Marketing/DevRel event for the 7th consecutive year, after the record participation of 1,000+ attendees in 2021.  DevRelX is a learning and sharing zone, committed to elevating the understanding of developer audiences and industry trends. A space where regardless of their experience level, everyone gets to access and share knowledge.  

This year’s event is an interactive experience of knowledge and expertise sharing, which puts the DevRelX community at its centre. The DevRelX Summit will take place on October 12 & 13 2022, with:

  • Panels
  • Community-led sessions
  • Lightning talks
  • Exclusive sessions and leadership workshops

Developer-focused professionals are invited to join the 2-day schedule
Full agenda follows: 

October 12 | Milestone Day | 8 am PT.

The first day, “Milestone Day” is invite-only. It is addressed to DevRel strategists, senior managers, seasoned DevRels, and CXOs. Anyone who wants to participate can request an invite via this link.

The Milestone day will offer participants strategic conversations, master classes, and workshops presented by industry pioneers and experts.

October 13 | Community Day | 8 am PT.

The second day, “Community Day”, is open to community advocates at heart. Anyone who believes that a community-centric mindset is the foundation of developer relations can get their ticket via this link.

The Community day will be full of developer community conversations, learning and connecting with peers.

Join the DevRelX Summit, for its 7th consecutive year – the best one yet!

Here is the full agenda:

DevRelX Summit Agenda

77% of all developers are involved in DevOps

About DevOps

More and more developers are getting involved in DevOps, with an eye on the ultimate DevOps end goal – to streamline the software delivery process. 

Although lacking a widely-accepted, universal definition, DevOps is in essence a set of practices that enable developers to release small but frequent software updates, reliably and safely. These practices are supported by a broader DevOps culture: activities, technologies, and dedicated platforms which work together to achieve the overarching DevOps goal: to streamline the software delivery process. 

In this short blog post, we’ll be sharing some key highlights from our latest global survey wave and the answers of 14,000 developers who responded to questions related to DevOps between December 2021 and February 2022. Also, we’ll be looking at findings from the “Who is into DevOps?” chapter of our 19th Edition State of the Developer Nation free report.

If reading this leaves you wanting to dive deeper into our DevOps insights, we are happy to let you know that we have extended our DevOps research to provide answers to questions like:

  • The DevOps technologies and new tools developers have evaluated, including the top vendors: Atlassian, AWS, Azure, GitHub, GitLab, Google Cloud, Heroku, JFrog, Oracle
  • The specific DevOps products or plans developers are using
  • How application security is handled across organisations
  • Which vendors’ application security tools they are using
  • The processes developers use to secure their cloud-native applications and 
  • Developers’ top security challenges

If you or your team are working on answering these DevOps questions, we will be happy to help you. Just get in touch

What are the latest insights on DevOps?

In our latest report “Landscape and trends in DevOps” we look at the current landscape and trends within DevOps from the developers’ perspective. We aim to understand who these developers are, look at what DevOps activities they’re involved in, and whether increased DevOps adoption really leads to higher software delivery process performance.

Here are the main highlights from the analysis: 

  • 77% of the surveyed developers are involved in DevOps
  • Involvement in multiple DevOps activities/technologies is predictive of higher software delivery performance
  • The average number of DevOps technologies used by DevOps practitioners has increased from 4.2 to 4.6 from Q3 2021 to Q1 2022. 

The last highlight means that the number of technologies used by DevOps practitioners has increased by nearly 10%. But DevOps practitioners are gradually exposed to a greater depth of activities too. Looking at each DevOps activity separately, we can see a significant increase in involvement across the board over the past 6 months:

involvement in DevOps-related activities has increased noticeably on the past six months

You can download the full preview of this report here or contact us to access all insights.

Who is into DevOps?

To answer this question and the ones that followed it, we asked developers whether they are involved in any of the activities that commonly fall under the DevOps spectrum, ranging from continuous integration and deployment to application and infrastructure monitoring. For the purposes of this blog post, we only consider developers who are professionals in at least one of the software areas they are active in. All the insights in this section come from our State of the Developer Nation 19th edition which was published on Q3 2020. You can contact us for all the latest insights.  

The first thing to note is that the adoption of DevOps practices is widespread among professionals, perhaps even more so than one might expect, given that the DevOps movement is relatively new. According to our data, the vast majority of professional developers (82%) are involved in DevOps in one way or another. For perspective, just over half (52%) of non-professionals are involved in any of the DevOps activities on our list.

Which of the following development activities are you involved in?

The vast majority of professional developers are involved in DevOps, but do not necessarily consider themselves DevOps practitioners

On a separate view of engagement with DevOps in our survey, only one in five developers reported working on DevOps when they were explicitly asked about their involvement in several emerging areas, including blockchain applications and quantum computing, among others. Even if we include those who said that they are learning about or are interested in DevOps, no more than 65% consider themselves to be engaged with the area. This signals that a large portion of the developer population has already adopted DevOps practices but does not necessarily self-identify with the term.

Focussing on the individual steps of the DevOps lifecycle, we find that developers are first and foremost involved in the fundamental activity of releasing frequent but small software updates. The most popular development process related to DevOps is continuous integration (CI), practised by 40% of respondents. Another 37% use continuous delivery or deployment (CD), which expands upon CI by automatically deploying all code changes to staging or production environments.

However, full automation of the software release process – and therefore true commitment to the DevOps culture – is far from a reality. While more than half (52%) of developers use CI or CD to streamline parts of their workflow, only 25% use both practices to automate all steps between integrating code changes into a central repository through to production deployment. As it turns out, developers are still sceptical about fully automated CI/CD pipelines. This is evident by the fact that nearly 40% of them manually give the green light for code deployments to be promoted to production.

Application and infrastructure monitoring, performed by 39% of developers, is one of the most common development practices, but not so much infrastructure provisioning and management (27%), which is still the realm of IT managers and system administrators. Similarly, creating automated tests (25%) and building CI/CD pipelines (23%) are rather specialised tasks, carried out predominantly by quality assurance professionals and solution architects, respectively.

Talking about organisational roles; our research reveals noticeable differences in the level of DevOps adoption, i.e. involvement in any DevOps-related activity, depending on the title that developers hold. First of all, technical company leaders – CIOs, CTOs, IT managers, and engineering team leads – report the highest level of involvement in DevOps activities. Not only do almost all developers with a technical leadership function, about 95% of them, have at least some participation in the DevOps lifecycle, but they are also simultaneously involved in a higher than the average number of DevOps activities (three vs two).

Involvement in DevOps by company role

Programmers have largely adopted CI/CD processes, but not so much other DevOps practices

The next tier of the DevOps adoption ranking is mainly occupied by specialist roles, such as network security engineers, QA developers, and system administrators. Between 86% and 91% of developers holding these positions are in some way associated with the DevOps culture. We should note, however, that only architects – system, solution, software etc. – appear to be heavily involved in all phases of the DevOps lifecycle. All other specialists are primarily focused on activities relevant to their expertise. For example, system administrators are naturally focused on infrastructure provisioning and monitoring, whereas QA engineers create automated tests for CI/CD pipelines more than anything else.

Front-line coders and software developers, who represent the majority of respondents in our survey (61%), are also highly likely to be involved in DevOps activities – 81% of them are although not more often than the average professional (82%). Our data suggest that software developers are keen to adopt CI/CD processes, but not so much operational practices such as monitoring applications in production environments. Again, this indicates that the complete shift to the DevOps culture has not yet been achieved. Apart from responsibilities central to their role, programmers are not accountable for additional product lifecycle phases.

Another important indicator of the level of engagement with DevOps practices is the software sectors that developers are involved in. As with roles, we see some interesting variations in DevOps adoption across sectors. For example, close to 90% of developers who create extensions for third-party ecosystems or backend services are into DevOps, as opposed to less than 80% of game developers.

Involvement in DevOps by software sector

That is partly explained by the extensive coding experience required to implement the DevOps model. We know from our data that DevOps practitioners are far more experienced coders than developers who are not involved in any DevOps-related activity. And developers working on apps for third-party ecosystems, backend services, or industrial IoT projects are among the most experienced in the software economy: up to 85% of them have three or more years of coding experience. In comparison, no more than 73% of game developers have the same level of expertise.

Nonetheless, we find that desktop app developers report relatively low adoption of DevOps practices, even though they are highly experienced professionals – 82% of them have at least three years of experience in software development. This points to limited alignment with the key benefits of DevOps more than anything else. Desktop applications typically receive updates at a lower frequency than applications running on other environments, e.g. servers. Therefore, the fundamental DevOps strategy of releasing small software updates at high velocity is not entirely applicable to desktop application projects.

In conclusion, DevOps signifies a cultural shift whereby developers from different teams work closely together with an aim to deliver software faster and more reliably. The practices of the DevOps model are already widely adopted among professional developers across software sectors and organisational roles, although with some significant variations in the focus on specific activities. These variations reveal, in some cases, that true commitment to the DevOps culture is not yet achieved; many developers are still focused on the core aspects of their role instead of assuming responsibility for additional phases of the product life cycle.

Want more DevOps insights? Get in touch and we can work together on all the questions you need to answer to optimise your strategy. 

Who is using low-code / no-code tools?

This is a chapter from our latest State of the Developer Nation 22nd Edition, which is free to download. You can watch our Lightning Session on the key findings and also read below for the whole report and insights on low-code / no-code tools.

Low-code/no-code (LCNC) tools provide a visual approach to software development, abstracting and automating parts of the application development process. This allows those without prior software development experience to create custom applications and provides potential time- and cost-saving for professional developers. In this chapter, we investigate the extent to which developers are using LCNC tools, showing differences according to professional status, geographical regions, and experience levels.

When it comes to reducing development overheads, addressing the challenge of finding skilled developers, and accelerating taking software to market, LCNC tools are becoming increasingly attractive. The sophistication of these tools is increasing rapidly, providing the potential to significantly disrupt the software industry. This begs the question, to what extent are developers1 using LCNC tools for their development projects?

We begin by separating developers according to their professional status – differentiating professionals from non-professionals, who are hobbyists and/or students. We excluded from our sample those who indicated that they were unsure about what share of their development work was done using LCNC tools. Just over half (54-55%) of developers in each group report that they are not using LCNC tools at all for their development work. This proportion is marginally lower for non-professionals who are students (55% of those who are exclusively students and 53% who are students and hobbyists) than non-professionals who identify as exclusively hobbyists (57%).

46% of professional developers use low-code/no-code tools for some portion of their development work

State of the Developer Nation 22nd Edition

The proportion of developers who do use LCNC tools does not differ across groups (46% of professionals vs 45% of non-professionals). This highlights that LCNC tools are finding traction among those less likely to be familiar with coding and that use-cases within professional software development are also common.

As experience increases, developers are less likely to use LCNC tools at all. This is particularly true among those with more than ten years of experience. These tools are often framed as being best suited for simple programming tasks. Hence, the complexity of development work assigned to more experienced developers may be less appropriate for LCNC approaches. Furthermore, experienced developers are likely to have mastery over simpler coding tasks, which leaves little room for the efficiency gains that LCNC tools are often heralded for.

Using LCNC tools without a degree of accompanying manual coding is highly uncommon across all experience levels. The proportion of developers who use LCNC tools for a small amount (up to a quarter) of their development work remains relatively constant (between 17-24%) across the experience spectrum. Therefore, LCNC’s most likely role is as an occasional adjunct to existing coding tools, regardless of developers’ experience.

Experienced developers, particularly those with more than 10 years of experience, are the least likely to use LCNC tools

State of the Developer Nation 22nd Edition

More extensive use of LCNC tools, i.e. for between one-quarter and three-quarters of all development activity, peaks slightly for those with around three to ten years of experience, revealing that it is early to mid-experience developers, rather than newcomers who are most likely to elevate LCNC tools’ status to essential. This is perhaps due to the recognised career importance of gaining traditional development experience, before reducing reliance on writing code. Only 2-4% of developers across all experience levels use LCNC tools for 75% or more of their development tasks, indicating that it is highly uncommon to shift the balance heavily towards LCNC-driven development.

Our data reveal notable differences in adoption and engagement with LCNC tools across different geographic regions. The Greater China area emerges as the region in which developers are most likely to be using LCNC approaches. 69% of developers in this region report using LCNC tools, compared to the global average of 46%. This suggests that the Chinese LCNC tool market has transitioned from an introduction phase to a growth phase. According to Mendix’s State of Low-Code report, IT professionals in China are the most likely to suggest that low-code is a trend their organisation can’t afford to miss (84% compared to 72% globally). Non-developer, or citizen developer, audiences also likely account for a large part of LCNC’s growth. However, as in all regions, the majority of bona fide software developers in the Greater China area currently use LCNC tools for less than half of their overall development work. It remains to be seen whether their reliance on such tools will also expand as the market and tools mature.

19% of developers in North America use Low-Code/No-Code tools for more than half of their coding work – almost twice the global average of 10%

North America has the second-highest LCNC tool adoption rate and stands out for the proportion of developers using LCNC tools to conduct more than half of their overall development work – 19% of developers here report that their use of LCNC tools outweighs their manual coding (comprising 13% using them for half to three-quarters of development work and 6% using them for more than three-quarters); almost double the global average of 10%. Hence, North America appears to be at the forefront of the LCNC movement, providing the strongest evidence that these tools can supplant traditional development approaches – even in a region where 81% of developers identify as professionals.

South Asia, the Middle East and Africa, and East Asia excluding Greater China are all above the global average in terms of LCNC tool adoption. Despite considerable uptake in these regions, LCNC products have not matured to the point where their use is a dominating feature of developers’ processes. Regions such as Western Europe and Israel, Oceania, Eastern Europe, and South America are all below the global average in terms of LCNC tool adoption.

The shortfall in these regions is particularly linked to smaller than average proportions using LCNC tools for more than 25% of their development work. The proportion using them for less than a quarter of their work is more comparable to the global average, suggesting that the market is still in its introductory phase in these regions – developers are evaluating the tools but are yet to rely on them for a substantial portion of their work.

Access the full free report to dive into insights on:

  • Language Communities
  • Understanding Developer Personalities
  • Who is using low-code / no-code tools
  • Spotlight on China and the Rest of East Asia
  • How developers generate revenue
  • Emerging technologies

If you have questions about the data above, want more or want to explore other topic areas we cover, talk to us.

Using SlashData Deep Dives to boost Developer Experience

When asked about why we do what we do, there’s always one response: we love solving problems for the industry and our clients. 

Our mission is to help our clients understand what the market looks like, what developers need, what excites developers and what doesn’t and what they expect from our clients’ products and the developer programs that go along with them. So, when we are approached with a request for some custom work, we roll up our sleeves and dive deep into the data.

In this blog post, we’ll look together into such a request and:

  • What the client asked
  • How we approached it
  • What we offered 
  • How the client solved the problem.

Let’s see how this client, a household name we’ll call “Client”, which is a company among the Top 5 in tech and one of the largest in the world, worked with us to improve their Developer Experience.

Knock knock – The Question

The client chose to work with us to address developer experience. They already had access to our research showing how their satisfaction level compares against their competitors, but what they wanted was to understand what drives developer satisfaction with their product and what they can do to improve it.

What was the goal/challenge you were looking to accomplish?

The product we wanted was a custom project. We’re always really interested in the health of the developer experience. And so we use the Developer Program Benchmarking report as one of the indicators of the health of the Client developer experience. Within that, we are also interested in the adoption and engagement [of our product]. But within my team, we mostly focus on satisfaction as a proxy metric for developer experience.
When we decided to do this custom project last year, it really was to understand “what is moving our satisfaction up or down?” and “what are some of the levers that we can adjust in order to improve our developer experience?”
Some of this data is confirming things that we already know. And some of it is providing new insights. Both of those are valuable use cases for us.

This report helped us not look at developer experience in a vacuum, but benchmark it against the industry.

Client representative

Why did you choose SlashData?

Part of that is the sample size. And I think the trusted relationship we already have. Also, I think this ties back into why do we choose the Developer Programs Benchmarking report. The competitive analysis in that report is important to us. While we didn’t focus on that in the deep dive, I do think that is one of the reasons why this data is helpful so that we’re not always looking at Client experience in a vacuum, but we can actually as the report says “benchmark it against the industry experience” as well.

The answer

After we looked at what questions our client has, we took a step back and looked at the data points that could help us find the answers. There were several data points to choose from, as we survey 30,000+ developers annually on 11 areas of interest.

How did our data solve your problem/challenge overall?

The area where we found it most useful is getting that cross-section of region, experience level, and product area. So we looked at that data. The place where it becomes a little harder in our process is making those insights actionable within our company. Part of our job is to provide the data and then folks act on it themselves. I think that Client Developer Relations, as a whole, is still thinking about “how do we make this data digestible and more centralised?”.
SlashData is a big data source for us. But there’s a lot of information always coming in at us, around developer experience. We’re still trying to navigate how we make that useful and easily actionable for our people. I don’t think we’re there yet. I think we’re at the point where we’re thinking “I want data to do my job better”. And then, we’re at “wow, okay, well, there’s a lot of data. What do we do now?”.

What decisions did you make using the data/research?

What we wanted to focus more on were the top three things that are important to developers this year. I don’t always have visibility into the TA level on what decisions might be made from this data. That’s also something that we want to do better. It’s also hard though because we don’t always expect that there will be a leader who’s going to take this and say “I now declare, we all must focus on this”.
We are equally happy if a single engineer sees this data and then goes and makes a change in the parts that they affect. That alone makes the overall developer experience better. There’s this interesting intersection of leadership use and individual contributor use. We know that there’s value to both sides, but we don’t necessarily track what that value is.

Working together

Seamless cooperation is key to bringing in good results. That’s why we wanted to know how our client felt about working with us on this project.

What did you like about the process of working with SlashData?

I think that Slashdata is a good partner. Especially when we focus on discovery. We had a case last year when we didn’t necessarily know what we were looking for. Your response was to try out different things. Even when we asked for a random data table, you did not only deliver it, but you also provided a comprehensive analysis and different ways that we could look at the data. Last year we focused a lot on regional topics but we also broke it down by product area. And then at the end of that, we decided that we didn’t care so much about the region. What we needed to focus on more is the product area. We have that partnership where we can do some exploration, and then have things work out well. Even if they don’t work out well, we continue from there. That’s a really important part of this piece. The flexibility is really important to us, and just as much, your responsiveness.

How would you describe the service quality?

I think that’s excellent. We’re not always super buttoned up on what we want and that causes a lot more work on your end, but it’s handled well. I feel like you have helped us navigate that a lot.

What are the things you found challenging when working with SlashData?

We don’t always know what we’re looking for. We are relying on you, the data analysts’ expertise to help guide us.
We need the expertise, but you don’t know the business goals. And it’s challenging to try to find that middle ground where I can articulate the business goals well enough for you to provide the expertise and help us decide on the right metrics or analysis that would prove to be useful information for those business goals.

This interview is part 2 of the “How we work with our clients” series. The product this client worked with was a custom project, along with Developer Program Benchmarking data. You can also see how Okta managed to broaden its developer network using our Developer Program Benchmarking.

Working on a new initiative or want to make sure your product will win developers’ hearts? Talk to us.

State of the Developer Nation: Coding language popularity, China’s developer market, how developers make revenue, and more!

The 22nd Developer Nation global survey from SlashData reached more than 20,000 developers in 166 countries. Its findings are bundled in a free “State of the Developer Nation” report. 

This research report delves into key developer trends for Q1 2022, taking a particular interest in the following:

  1. Language communities – An update
  2. Understanding developer personalities
  3. Who is using low-code/no-code tools?
  4. Spotlight on China and the rest of East Asia
  5. How developers generate revenues
  6. Emerging technologies

Here are some highlights from the report, guaranteed to intrigue your curiosity: 

Language communities – An update

  • JavaScript remains the most popular programming language for the tenth survey in a row, with close to 17.5M developers worldwide using it. Python has remained the second most widely adopted language behind JavaScript. Python now counts 15.7M users.
  • Go and Ruby are important languages in backend development but Go has grown more than twice as fast in the past year in absolute terms.

Rust has nearly tripled in size in the past 24 months, from just 0.6M developers in Q1 2020 to 2.2M in Q1 2022.

State of the Developer Nation 22nd Edition

Spotlight on China and the rest of East Asia

  • More than a quarter of developers in Greater China (26%) and the rest of East Asia (27%) don’t use Stack Overflow, which is more than three times the rate of developers in the rest of the world (8%).
  • The Greater China area has a relatively low concentration of highly- experienced developers (16+ years of development) when compared to developers in the rest of East Asia and the rest of the world.
  • More than half of Chinese developers have learned how to code via undergraduate degrees in computing, which is about 10 percentage points more than developers in the rest of East Asia and the rest of the world.

How developers generate revenues

  • Contracted development is the revenue model of choice across all industry verticals, used by nearly a third (31%) of professional developers.
  • Less than one in ten (7%) professional developers are generating revenue from selling data.
  • Usage of the advertising revenue model declines as companies grow in size.
  • Developers working for large enterprises (5K+ employees) tend to use
    multiple revenue models less often than developers in smaller companies.

Below we have included a few graphs that illustrate some of the findings.

You can download the full report for free and access all data and insights within.

If you need additional information or looking to understand developer preferences’, please get in touch with us and we will dive into it together.

How to engage developers – straight from tech experts’ experiences

Developer Marketing & Relations: The Essential Guide just published its 3rd edition

Quick history: In 2018 SlashData decided to publish a book titled “Developer Marketing: The Essential Guide”, seeing the lack of education in developer marketing and relations roles and activities. In that book, industry leaders from the world’s largest companies shared their “things to do and things not to do” experiences. Each chapter had its own author, focusing on the topic they knew best.

Fast-forward to today. Thousands of books have already been sold. The industry evolves fast. Not all ground has been covered. Therefore, an updated edition was much needed. This is why the “Developer Marketing & Relations: The Essential Guide – 3rd Edition” has been launched.

The 3rd Edition features 9 new chapters and 1 revised chapter since the first 2018 edition. It is a much more complete read and covers most of the topics that dev marketing and DevRel professionals will come across in their professional life.

The book can be read cover to cover or readers can pick the topics they are interested in. Each chapter addresses a specific topic written by an author from a major company. Some of the topics are community (+ how to make it inclusive), building personas, building developer programs, developer events, connecting with developers and many more from 24 authors and 17 Industry-Leading companies.

The book’s aim is to educate and help professionals push their careers forward. All profits from book sales are donated to worthy organisations: Code.org, Girls Who Code, Black Girls Code and CoderDojo. So far we have donated more than £7,000.

To support the dev marketing and DevRel community at challenging times, the book price is reduced by 50% to make it accessible to everyone: $9.99 for the paperback and $4.99 for the digital edition.

The book is available through Amazon in Paperback and Kindle and through the book website in ePub.  

For more details, see the book website.

If you are a journalist and want to spread the word and/or write a review of the book, you can claim a free copy.

Companies the book authors work in:
Amazon Web Services, apidays, ARM, Atlassian, Facebook, Google, Microsoft, Nutanix, Oracle, Qualcomm, Salesforce, Samsung, SAP, TomTom, Unity, VISA, VMWare

Hot off the Press: Developers’ needs due to COVID-19, Open Source, Languageds, DevOps and more

What do developers value in open source?
How have their needs changed due to COVID-19?

The 19th Developer Economics global survey wave ran from June to August 2020 and reached more than 17,000 developers in 159 countries. Hot off the press “State of the Developer Nation” report presents developer trends for Q3 2020 and beyond.

The report is free  to access and focuses on six major topics, providing answers to questions like these:

  1. Developers’ extra needs due to COVID-19
  2. Programming language communities – an update
  3. Why do developers adopt or reject cloud technologies?
  4. Who is into DevOps?
  5. What do developers value in open source?
  6. Emerging technologies

Some highlights to spark your curiosity:

state of developer nation highlights

 

Developers’ extra needs due to COVID-19

  • Four in ten developers report that they need more flexibility in working hours/workload as a consequence of COVID-19.
  • Developers responsible for tooling specifications and for approving budgets and expenses are in the greatest need of increased security, performance, and cloud space.

What do developers value in open source?

  • Developers appreciate collaborating and interacting with the open-source community more than contributing to open-source projects.
  • South Asian developers highly value contributing to open-source projects, positioning this region to drive the next wave of open-source development.
  • Developers who are building apps and extensions for third party ecosystems, on average, value contributing and forking more than developers in other sectors.

Who is into DevOps? 

  • DevOps has reached mainstream adoption.
  • The vast majority of professional developers (more than 80%) are involved in DevOps in one way or another.
  • Continuous integration (CI) and continuous deployment (CD) are two of the most common DevOps practices, but only one in four developers use both to fully automate their workflow.

Download the full report here.

The report is free to download for all community members including developers and industry enthusiasts.

6 reasons to be part of the Future Developer Summit

We’re currently on countdown mode. The Future Developer Summit is coming on April 7-8 to help developer marketing and relations leaders engage open-source developers.

But to us and our participants, it’s more than that. We are not just creating an event unlike the rest. We are creating a community of handpicked professionals who work together to push the boundaries of developer programs. As we are designing all aspects of the event, from working with speakers about their presentations to the music that will play as directors and industry leaders go through their challenges with their industry peers, we try to have all our efforts answer the trickiest of questions:

  • How will we deliver real, tangible value to our community members to empower them to shape the future of developer programs? and
  • Why would someone want to come to our event?

Well, here’s the answer:

  1. It’s an exclusive, invite-only event. This means you have the chance to share best practices with other leaders in the developer marketing and relations world, as senior peer-to-senior peer.
  2. Experience the power of a community of director-level professionals who design developer strategies together. The Future Developer Summit is building a community for developer marketing and developer relations leaders, who acknowledge and embrace the value of collective effort and its impact on individual work. After the event, you will get back to work enriched with insights, new knowledge and ideas to maximize the impact of your developer program.
  3. It’s a full pack learning experience. And it’s definitely not an endless line of slide after slide. We have designed a variety of sessions so that you can make most of your time onsite. We have prepared for you 11 lightning talks, 4 keynotes, 3 fireside chats, 3 panels, and 2 interactive workshops where you will work in groups side by side with your industry peers. Plus: it is participatory. We want you to share your ideas or challenges. Polyphony is the only way forward for us and an integral part of our community.
  4. It’s aligned with the industry pulse. Each Summit covers a different aspect of the developer marketing and developer relations industry and aims to start a meaningful conversation for the community and its leaders. For April, the theme is focused on engaging open-source developers.
  5. It’s a platform for new ideas to grow. The interactive workshops combined with a diverse attendee roster help plant the seeds for innovative ideas to turn into strategies and push towards the future. From the 2017 Future Developer Summit, the “Developer Marketing and Relations: The Essential Guide” was born and is now, with its second edition, the most inclusive book and go-to guide for anyone who seeks to navigate and advance their career in the developer marketing and relations industry.
  6. It’s personal. A great opportunity to know the people behind the roles. People with whom you face the same challenges, in the same industry. People you can teach and learn from.
    Plus: The speaker lineup is outstanding! All Future Developer Summit speakers are developer marketing and relations leaders in the world’s biggest organisations such as Microsoft, IBM, Facebook, GitHub and more.

We take pride in designing an immersive developer marketing learning and community partaking experience. Our latest Future Developer Summit earned an NPS score of 94 and put smiles on many faces, including ours. Why such a high score? We’ll let our attendees answer that for us:

I met some awesome people, derived practical and useful knowledge, and felt a lot of love from folks who listened to my talk. You created a wonderful, safe environment that allowed for a real, candid conversation. I think the focus on D&I was a major factor in this.” – Tim Falls, Digital Ocean

This was an awesome event because the attendees are all leaders in Developer Relations at their company. Great networking and data-sharing opportunity! Thanks /Data!” – Larry McDonough, VMware

Future Developer Summit is an excellent resource for learning and networking with developer marketing leaders #HighQuality” – Jason Fournier, You.i TV

My annual moment to reconnect with a community of like-minded practitioners in a meaningful, focused manner.” – Katie Miller, Google

Great event – I have learned so much and met amazing people.” – Amanda Whaley, Cisco

Want more? Watch our video (warning: it’s a big teaser) and head over to futuredeveloper.io.

Tech professionals and directors group photo at the Future Developer Summit
2019 Attendees