Search Results

This article continues the series where we present key analysis and insights from the latest State of the Developer Nation public report. You can read the previous 2 instalments on developer communities and developers working on everyday electronic devices. In this chapter, we offer insight into how developers perceive the future of generative AI; specifically how it relates to their role as a developer. We all remember back in March when prominent leaders, researchers, and figures in tech, most notably Elon Musk and Steve Wozniak, signed a letter advocating for a six-month pause of giant artificial intelligence (AI) experiments. Despite the letter prompting a wide discussion and raising both ethical and practical concerns that were acknowledged by many in the field, few were surprised that the letter had a negligible impact on slowing the pace of research. Now, approximately six months following the letter’s initial publication, we check in with those who are among the closest to the subject in question: developers. In our latest Developer Nation survey, we collected insights, perspectives, and real-world experiences from over 17,000 developers worldwide, delving into the impact of generative AI on their careers and work now and in the future. Various studies that measured AI’s impact on worker productivity in different roles have been published this year. In this chapter, we do not delve into productivity metrics, but rather, we present developers’ views and perceptions about how generative AI will affect their productivity, work, and the world. 80% of developers believe that Generative AI will increase their potential and productivity at work Regarding AI’s impact on their work, developers are overwhelmingly optimistic. The vast majority (80%) of them agree or strongly agree that AI will increase their potential and productivity, while 70% agree or strongly agree that it will give them access to new programming tools. Throughout our many years of tracking and researching developers’ preferences and behaviours, we have found that the community is incredibly heterogeneous. There is substantial variation in developers’ educational backgrounds, technology choices, and professional preferences. Hence, this remarkable consensus regarding the impact of AI on their workflow is striking. It sends a clear message about generative AI’s positive potential: only 7% of developers disagree or strongly disagree that AI’s net impact on the world will be positive! While generative AI’s potential is great, developers clearly still harbour some reservations as well. 61% of developers agree or strongly agree that generative AI raises many ethical concerns. While we did not ask our survey respondents to specifically identify which ethical concerns they are most preoccupied with, one of the primary ethical concerns regarding AI that has received considerable attention this past year is its potential to displace workers. Developers are somewhat split about generative AI’s potential to displace them in their current roles. 32% of developers strongly agree that AI will surpass their skills and render their jobs obsolete, while 40% either disagree or strongly disagree that this is actually a feasible outcome. How developers feel about AI’s potential to replace their jobs depends on a number of factors, but one critical factor is their current role. In the following section, we examine the differences in perceptions across various roles. Will Generative AI replace developers? Segmenting developers by ten of the most popular roles, we examine which roles have the highest concerns about potential replacement. CIOs, CTOs, and IT managers are the most likely (40%) to strongly agree that generative AI could surpass their skills and render their role obsolete. Initially, this result is somewhat counter-intuitive as managerial skills are unlikely to be replaced in the foreseeable future by generative AI due to the variety and complexity of tasks that managers often face. However, these specific roles are frequently responsible for monitoring a company's technology, infrastructure, and data for – among other metrics – accuracy, efficiency, security, and efficacy; all of which are quantifiable. While AI surpasses a human’s ability in terms of speed and accuracy of monitoring various quantitative metrics, we do not foresee a future where these roles are no longer present, rather, the technical aspect of the roles are altered; a notion supported by 41% of developers in these roles. These roles are more than likely going to evolve or be reimagined to compensate for the additional capacity granted by AI. Developers working or studying as data analysts, scientists, and/or researchers make up the next three roles that are most likely (37%-40%) to strongly agree their skills will be surpassed and their jobs could be rendered obsolete. However, roughly an equal or greater number of developers in these data-driven roles strongly disagree. Generative AI has made great strides in several areas, including data analysis and code generation. While the progress is impressive, what is equally striking is how difficult it can be to differentiate correct from false/hallucinated answers and incorrect analytical applications or interpretations, unless the developer has domain-specific knowledge. Hence, while these researcher and data-handling roles have already been substantially impacted by AI and will surely continue to be, developers are split on the future of these types of roles. On the opposite end of the spectrum, architects and programmers are the most likely to strongly disagree that their roles and skills can be replaced by generative AI. The majority of these developers, 61% and 55%, respectively, feel their role and skills are safe from the threat of generative AI. These developers are some of the most likely to be technical experts and recognise that while AI can excel at quantifiable solutions, complex or multi-faceted problems are likely to continue to require substantial human input for the foreseeable future. 61% and 55% of Architects and Programmers respectively, disagree or strongly disagree that Generative AI will surpass their skills and render their jobs obsolete. It is inevitable, however, that these roles will still feel its impact and influence in their work. Hence, in the next section, we take a look into who the developers are who feel that they can benefit from AI and gain access to additional tools through its use. Will AI allow developers to access new tools and technologies? One of the factors that significantly impacts developers’ perceptions on whether generative AI will allow them to use programming tools that they previously could not is their level of experience. Overwhelmingly, 80% of developers with less than a year of software development experience agree or strongly agree that AI will give them access to new tools that would otherwise not be available. The proportion of developers who agree steadily declines to 60% as developers gain more experience, where in turn, more experienced developers are more likely to strongly disagree with this sentiment. More experienced developers also have greater programming skills and are therefore less likely to expect that generative AI will create new opportunities for them to access additional tools. It is not a new phenomenon that younger, less experienced individuals enter a field or company and are more open to learning novel techniques or new methods; some of which can be in contrast to the established, institutionalised way of doing things. This distribution of developers' AI perspective below conforms to this trend and demonstrates that less experienced developers perceive AI in a different light compared to the more seasoned ones. However, a finding worth highlighting here is that the experts in the field – those with more than 16 years of experience – are the most likely (28%) to report being unsure, neither agreeing or disagreeing, about AI’s potential to provide them access to new tools. This degree of uncertainty from the most practised group of developers is a good indicator that the future of generative AI is still very much evolving and points to an exciting but somewhat uncertain future of how AI advancements will continue to shape the role of developers. This article is part of the developer insights offered in the State of the Developer Nation 25th Edition. You can access the full report which covers: 1. Language communities - An update 2. Creating A Sense Of Community - How Developers Interact And Engage With Their Peers 3. How Generative AI Will Affect Developers' Work 4. Web3 Unveiled - Exploring The Diverse Landscape Of Web3 Development Projects 5. From Code To Consumer Magic - The Software Developers Behind Our Everyday Electronic Devices 6. What Are People Building In AR/VR? Want to dive deeper into data on developer population, data and segmentation? Let’s talk.

Development communities like GitHub and StackOverflow are the bedrock of progress for all kinds of developers and their projects. Furthermore, many organisations curate their own communities to enhance developers’ experience with their products. In this post, taken out of SlashData’s public report “The State of the Developer Nation”, we’ll learn what developers look for when joining a technology-centric community and which factors encourage them to participate and engage more. What factors do developers consider when joining a technology-centric community? Developers primarily engage with technology-centric communities to learn. More than half (52%) consider the quality of available information to be one of the five most important factors to consider when joining a community. That’s considerably more than the next most popular factor, the availability of courses/training (38%), which, incidentally, also facilitates learning and knowledge-sharing. Developers primarily engage with technology-centric communities to learn – the quality of available information is by far the most important factor Interestingly, we see changes in importance among developers who didn’t select either of these two learning-related factors. In-person events (+6%), member-only benefits (+5%), links to industry (+4%), and online events (+4%) all increased in importance. This suggests that when developers aren’t there to learn, they are more likely to join a community in order to network. However, these factors are still among the least important for this group. A positive culture enables developers to get the most from their community experience Community culture is also important. 35% of developers consider the friendliness of a community when deciding to join, making this the third most important factor. Clearly, curating a welcoming and friendly experience should be a priority for community managers. In fact, it seems that a positive culture is an enabling factor in allowing information-seekers to get the most from their community experience: developers who prioritise the quality of information and having access to expert community members are more likely than average to also think that a positive culture is important. Further down the list, the platform on which the community is based is actually not that important when developers decide to join a technology-centric community. Only 21% of developers selected this option, making it the seventh most important factor, just ahead of recency and frequency of activity. However, as we will see later, the right platform can ignite greater engagement and participation. For now, though, we’ll take a closer look at which factors developers in different generations consider before joining a technology-centric community. As developers age, they become even more focused on the aspects of a community which facilitate learning. The quality of information present rises in importance the most — increasing from 47% amongst the youngest developers to 68% of the oldest. We see a similar – though less intense – story for the availability of courses/training, a friendly and welcoming culture, and expert community members. Once again, a positive culture is an enabler of accessing learning materials, and, as we will see later, also an enabler of increased engagement and participation. 68% of developers aged 45 and up consider the quality of information available when joining a community On the other hand, younger developers have subtly different preferences. They are more likely than the oldest developers to consider mentorship programmes, links to industry/recruiters, and membership benefits as being important factors. These younger developers are focused on the employment and the networking benefits of community membership. Younger developers are more focused than their older peers on the employment and the networking benefits of community membership Importantly, the youngest developers consider mentorship programmes to be more than 2.5 times as important as older developers (26% vs 10%), and mentorship programmes are the fifth most important factor to these developers, likely due to their focus on building their careers. Now, this creates a point of tension – how to attract older and more experienced developers to a community, and then engage them in mentorship programmes to help younger developers? Firstly, ensuring that communities meet older developers’ expectations around learning will go a long way to attracting them in the first place. However, to raise engagement for this group, we see that older developers who value mentorship opportunities are more than twice as likely than those who don’t to say that inviting their peers and friends and the availability of in-person events, contribute to increasing their participation levels. In a nutshell, the type of older developer who values mentorship is already predisposed to the networking benefits of a community. Identifying these older developers should be a priority for any community where demand for mentorships outstrips supply. You can access the full report here. What encourages developers to actively participate in a community? From joining a community to actively participating in it, we see large differences in what makes developers tick. A well-designed community platform – which is far down the list of factors that developers consider when joining a community – sits at the top when we ask about what encourages greater community participation. The time and effort that goes into selecting the right platform might not have immediate returns for growing a community, but it is likely to help to keep developers engaged and active. A well-designed platform is what encourages developers the most to actively participate in a community Participation is a two-way street. 27% of developers say that getting regular updates inspires greater engagement. Here, developers want to see activity from the community managers and founders. Looking at this from another direction: there’s likely nothing less inspiring than joining a community where the leaders aren’t themselves engaged. Indeed, further down the list, 17% of developers say that direct interaction with community leaders helps with their engagement. Strong leadership has benefits beyond day-to-day participation. Having a well-defined purpose for the community encourages more active participation for 26% of developers, and an inclusive and welcoming culture is encouraging for 25%. Interestingly, active moderation is a much less popular driver of engagement – only 15% of developers selected this, but those who did are much more likely than average to engage more in communities with a positive culture. A positive community culture not only encourages people to join but also keeps them engaged. This said, sometimes a heavy moderating hand is necessary – whilst developers might not always appreciate it, the alternative of a negative, exclusive, or toxic community culture is likely worse. Developers who value strong leadership in a community are often less engaged by games, quizzes, and prizes It’s not only good vibes that encourage greater participation; prizes and rewards (26%) appear to be a powerful lever in encouraging greater community involvement, with fun activities close behind (22%). However, developers who are encouraged to participate through factors relating to strong leadership and expertise – positive culture, well-defined purpose, direct interaction with leaders, and having access to recognised experts – are often much less inspired to participate by prizes, activities, and polls and quizzes, whilst the inverse is also true. This points to there being two distinct groups of developers – those who engage ‘seriously’ and those who perhaps take a more whimsical approach to community engagement. For community organisers and contributors, it’s important to understand which mindset a community tends towards: a focus on fun and games in a more serious community may appear to lack authenticity and gravitas, whereas taking a more sober tone may exclude those with a lighter agenda. For developers of all backgrounds and skill levels, communities offer an opportunity not only to learn but also to connect. Different types of developers have different expectations for how they want to interact with their communities, but learning opportunities and a welcoming culture are consistently highly rated. This article is part of the developer insights offered in the State of the Developer Nation 25th Edition. You can access the full report which covers: 1. Language communities - An update 2. Creating A Sense Of Community - How Developers Interact And Engage With Their Peers 3. How Generative Ai Will Affect Developers' Work 4. Web3 Unveiled - Exploring The Diverse Landscape Of Web3 Development Projects 5. From Code To Consumer Magic - The Software Developers Behind Our Everyday Electronic Devices 6. What Are People Building In AR/VR? Want to dive deeper into data on developer population, data and segmentation? Let’s talk.

Sustainable software engineering (SSE) is the practice of minimising the environmental impact of software. It is an emerging discipline that integrates sustainability into software practices and architecture, hardware, and data centre design. The ultimate goal of SSE is to reduce the amount of carbon emissions that software applications are responsible for by integrating various approaches to the software development lifecycle. Commonly, SSE is implemented by utilising more efficient or ‘green’ coding practices, but there are a variety of approaches available to organisations and developers alike. In our recent report titled “Who’s integrating sustainable software engineering principles?”, which was based on data collected from the 24th edition of our Developer Nation survey, we discovered that 76% of developers sometimes or always implement at least one SSE principle and that this rises to 82% amongst professional developers. In this blog post, we take a closer look at how developers’ roles, decision-making power and involvement in DevOps activities influence their utilisation of SSE principles. Involvement in DevOps* is a powerful predictor of utilising SSE principles in development projects. These developers are responsible for implementing SSE principles, which takes place at an infrastructural level. This said, as we will soon see, developers higher up the chain of command report using SSE principles more often than DevOps practitioners, with decision-makers being the most likely to adopt such approaches. This demonstrates that whilst decision-makers provide the impetus for adoption, it’s those in DevOps roles who undertake the implementation. Developers involved in DevOps are considerably more likely to utilise SSE than those not involved Indeed, we see that developers involved in DevOps are much more likely to utilise SSE approaches in some capacity than those not involved. The changes in overall SSE utilisation amongst developers doing different DevOps activities, such as continuous integration or automated testing, are not meaningfully different. However, when taking a more granular look at precisely which SSE principles are implemented by developers involved in different DevOps sub-disciplines, we see that it’s those who programmatically provision and manage infrastructure and those who monitor performance and test for security vulnerabilities who implement the widest variety of SSE principles. Developers involved in these stages of the DevOps lifecycle appear to be particularly well-placed to have maximum impact, and vendors should ensure that any SSE tools and products integrate well with these parts of the DevOps technology stack. *In our Developer Nation surveys, we don’t ask developers to self-identify as being involved in DevOps. Rather, we determine their involvement by asking them whether or not they undertake different DevOps-related activities, such as using CI/CD or creating automated tests. Note: The Developer Nation survey is now live. You can respond and help us better understand developers and produce insights that help you address developers’ needs. Our data also show that the more involved developers become in tool purchasing decisions, the more likely they are to integrate SSE principles into their development projects. The reason behind this is twofold: SSE is a relatively new discipline, and so those who are not currently buying tools or components are less likely to have had the opportunity to integrate tools which facilitate SSE development into their projects. More senior developers have a better understanding of the cost-savings and other benefits of adopting SSE principles, and so a larger incentive to integrate such approaches. They also have the power or influence to effect such a change. Senior decision-makers are the most likely to integrate SSE principles into their development projects We can see the effect of decision-making seniority reflected in the usage of SSE by developers in different roles. 91% of CIOs / CTOs / IT managers utilise SSE approaches, but 78% of developers in unspecialised programmer roles do as well. Currently, the implementation of SSE principles is of strategic concern, with a high-level implementation rather than taking place closer to the code. It may be that SSE approaches will follow secure coding practises and ‘shift-left’ as developers take more personal responsibility for the sustainability of their code in the future. DevOps practitioners and decision-makers will still need to be involved though – organisational and infrastructural implementation of SSE principles will continue to have a large impact. For now, though, SSE practices are typically implemented in the domain of specialists such as DevOps practitioners and decision-makers, and we see that developers in these roles are often motivated by environmental concerns and believe they have a part to play in combating climate change. Vendors wishing to encourage the adoption of SSE products and principles may find traction in appealing to the consciences of decision-makers in organisations. We also find that DevOps engineers and other specialists, as well as CEOs, are most challenged by measuring the impact of integrating SSE into their development projects. As companies cannot manage what they are unable to measure, it is clear that the lack of a metric is a key hurdle in SSE being more broadly adopted. Removing this pain point could also act as a push to drive adoption. In our Developer Nation survey, we also asked which SSE principles developers are integrating. The list of SSE principles included activities such as creating carbon-efficient software, minimising data transmission, or optimising code. Looking more closely at which principles are being integrated by developers in different roles, we see that those in managerial positions are among the most likely to integrate every SSE principle we asked about in our latest global developer survey. However, given that few developers in leadership positions are responsible for the implementation, many developers who are closer to the code disagree. Programmers, architects, and DevOps engineers all integrate most of the SSE principles we ask about much less often than average. This suggests that there is a disconnect between the SSE principles that leadership wishes to adopt and what is actually implemented. A closer look at DevOps practitioners reveals a further surprise – as we saw previously, these developers are some of the most likely to integrate SSE principles overall, but they are actually less likely than average to integrate many specific SSE principles. This indicates that DevOps engineers are selective about which principles to integrate. This isn’t the whole story, though. Other specialists such as embedded developers or network, hardware and site reliability engineers integrate the widest range of SSE principles into their development projects – though the cumulative impact of the small numbers of developers in these niche roles is small, they are highly active in the SSE space and represent a cohort of early adopters with a wide range of involvement in SSE. In this post, we’ve learnt that SSE remains in the realm of specialists and leadership, and whilst software development tool companies should cater to the needs of developers in these roles, it’s also worth considering how to drive wider adoption of SSE. Should you be interested in learning more, we take a closer look at developers’ motivations and challenges in the report. For now, SSE sits firmly in the domain of specialist developers and leadership Did you like this post? Discover more about our research and have your say in the Developer Nation survey. #sse #sustaiability #sustainablesoftwareengineering

In this post, taken out of SlashData’s public report “The State of the Developer Nation”, we dive into the world of consumer electronics and explore the profiles of developers who target different types of applications in this space. We focus on comparing their experience levels and their involvement across other sectors. What developers are working on Today, the number of Internet of Things (IoT) connections (15B in 2023) outnumbers humans and is forecasted to nearly double by 2030. A subset of this space, consumer electronics (CE), is focused on devices that are targeted towards consumers and often individual use. Examples of CE devices range from home security devices such as digital door locks to cameras and fitness trackers. 4.4M Developers are involved in Consumer Electronics projects As of Q3 2023, we estimate that there are 4.4M developers who work on CE projects, making up 11% of the total developer population. In our latest Developer Nation survey, we asked developers who are involved in this space about the CE categories that they are targeting with their applications. In first place, 28% report that they are working on software for security and access products such as door locks and CCTV systems. This is closely followed by communication devices (26%), network equipment (26%), energy appliances (25%), and entertainment systems (23%). These categories stand out far above the rest, with the next most popular category – home appliances – being targeted by 18% of the developers in the CE space. The many similarities and differences between the top CE categories are reflected in the profiles of the developers who target them with their applications. One of the most interesting aspects to consider is how experience in software development impacts the projects that these developers take on. Developers’ experience We find that those who target energy appliances have the highest level of experience in CE projects*. More specifically, these developers have an average of 3.9 years of experience in this space, which is significantly higher than that of their counterparts who are not involved in energy appliances (3.1 years). This indicates that the specific challenges encountered in this category are more likely to require specialised knowledge of the CE space than across other categories. Having experience with other CE devices can be highly beneficial for development, as energy appliances need to integrate with other household systems and the energy grid. The projects that the developers who are targeting this category are much more likely than average to be smart (59% vs 43%) and have an app (49% vs 35%). Developers who target security and access products are highly experienced in general software development. Interestingly, developers who target security and access products have significantly more experience in software development (4.9 years) than in CE (3.4 years). This corresponds to the most significant gap between experience levels in these two groups. It indicates that working on security and access products is more likely than average to require experience in other development areas beyond CE. With above-average experience in software development, CE developers are involved in other areas of software development. The largest overlap comes from those involved in the industrial IoT (IIoT) development sector (43%). In particular, 56% of those involved in energy appliances also work on IIoT projects and are the most likely to do so. Using this as an example, a household energy management device only needs to manage the energy usage of one household, while an equivalent IIoT system may need to consider an entire manufacturing plant. While there are differences in scale, these two systems share the essence of what they are designed to do. This showcases the close relationship between these two sectors in the broader IoT ecosystem. Security and access On closer inspection of the overlap with IIoT, we see that only 28% of those who work on software targeted at entertainment systems are involved in IIoT projects. This is significantly below that of any other target category in the CE space. Instead, they are the most likely to develop games (36%) and have an above-average representation in the mobile sector (40%). Similar to the case of energy appliances and IIoT, there is a natural overlap between devices aimed at entertainment systems and these two sectors. For example, developers who develop software for smart speakers may also work on accompanying mobile applications. Developers leverage data science to enhance security and access products. Another interesting example can be seen among developers who target security and access products. We find that 32% of them are also involved in data science, which is significantly above average across the other categories (20%). This suggests that data from security devices is analysed in detail to improve the functionality of security and access products. For instance, advanced analytics can be used to detect suspicious access patterns in digital door locks and alert both users and authorities of potential intruders. * We measure this by comparing the median number of years that the developers within each category have worked on software projects. Medians are estimated from grouped frequency data. This article is part of the developer insights offered in the State of the Developer Nation 25th Edition. You can access the full report which covers: 1. Language communities - An update 2. Creating A Sense Of Community - How Developers Interact And Engage With Their Peers 3. How Generative Ai Will Affect Developers' Work 4. Web3 Unveiled - Exploring The Diverse Landscape Of Web3 Development Projects 5. From Code To Consumer Magic - The Software Developers Behind Our Everyday Electronic Devices 6. What Are People Building In AR/VR? Want to dive deeper into developer data on consumer electronics, IoT or Industrial IoT? Let’s talk.

SlashData’s Developer Program Benchmarking report provides annual insights into developer behavior and trends that help tech companies make better, data-driven decisions. Many Big Tech companies have come to trust our unique data insights in helping them understand developers better and shape their strategies. Here’s how one of them –Okta– is using SlashData’s Developer Program Benchmarking to stand out and unlock more developer opportunities. The Gap. Optimize Developer Strategies that Boost Okta’s Developer Community. Every tech company needs to have a better understanding of their developer-user base — so they can make more informed decisions. Plus, having a clearer view of the strengths and weaknesses of your developer programs will expose how you measure up against competitors and how to stand out. To achieve this, it becomes necessary to: Track your program adoption rate –anywhere in the world Stay on top of developer satisfaction with your programs See how competitor developer programs are scoring – what they’re doing right and the gaps you can capitalize on Measure the performance of your specific offerings based on what developers value …and so on. Tech companies like Okta are using SlashData’s Developer Program Benchmarking to do just that. “A Must-Have Resource for Developer Relations” “Over the years, I’ve used SlashData’s reports to understand and prioritize what matters to developers. I’ve found the reports quite helpful in terms of identifying areas for improvement and the impact of our investments. For example, when I was at Mozilla, we noticed our satisfaction score for blogs and newsletters wasn’t where we’d like it to be. So, we invested in creating a developer newsletter and improving the blog. And in 18 months, we saw our satisfaction score for this area rise to the top 3. This satisfaction score and other standard metrics (reach, opens, etc.) helped us determine how successful our program was. Now, at Okta, I’m again using the report to identify areas for improvement and will invest in our documentation, blog and website. SlashData reports give us a trendline that shows, over time, if and how these investments pay off, and allow us to make changes if we are not seeing results.” —Ali Spivak Sr. Director of Developer Relations, Okta [ex. Mozilla] The Results. Instead of second-guessing developers’ interests and neglecting areas of investments that count, Director of Developer Relations – Ali Spivak – could use SlashData’s reports to: Help determine areas of investment and to see –over time — how those investments impact developer adoption and satisfaction level Provide invaluable insights on how their program was performing and where their opportunities for growth lie Shape and augment the user research they were already conducting and focus more on specific areas that required attention Track developers’ satisfaction scores with their program and specific offerings Benchmark how Okta’s developer programs stack up against other developer programs to provide them with a model of improvement Help stakeholders understand what developers are experiencing and prioritizing, their needs, and also justify the investments made into developer programs Here’s How We Can Work Together to Build a Thriving Developer Ecosystem… In today’s diverse and complex developer ecosystem, there’s real power in knowing where to focus your efforts to help build a thriving developer community. That’s what SlashData’s Developer Program Benchmarking helps you achieve. With SlashData, you get: Data-Driven Insights for Effective Decision-making Data is the fuel that drives the engine of decision-making – as a data-driven company, we’re always aware of its immense value. So, when you come to us and share your current challenges, we work to help you see and understand how much difference data-backed decision-making can make. We’re always ready to engage and walk you through the data –so you can uncover and bridge the current gaps you’re experiencing. Client-Tailored Global Developer Survey SlashData’s Developer Program Benchmarking report is a syndicated research study available to tech companies who are subscribed to our program. It is based on data collected in our Global Developer Nation survey that’s fielded twice per year. If your developer program hasn’t been benchmarked, we will include it in the upcoming editions of our in-depth research study. There are many hidden potentials for your growth in engaging developers in a way that targets their needs and  improves their experiences. That’s why we survey about 20 developer programs every 6 months, as the list of programs benchmarked is ever-changing. This helps us learn more about what boosts satisfaction and adoption rates for developers. Full Access to Deliverables for Close Monitoring We provide full access to the agreed deliverables as soon as they get completed. These usually include a market landscape report, insights report specific to your company, and an interactive data dashboard that allows filtering and zeroing in on a particular developer segment. Our clients have found these reports quite useful in helping them shape and even augment the user research they are already conducting on their own. These deliverables will help you pinpoint the specific places you should be focusing on for in-depth user research. Plus, it provides areas of opportunities where you can exploit advantages over competition to stand out. Beyond ready to build stronger relationships with your developer community? Get in touch and we will dive in together in the solutions that will win developers’ hearts. #okradevelopers #okta #developerprograms #developerprogramsbenchmarking #slashdatadpb #okradeveloperprogram

With the ongoing effects of the recent global pandemic and the European energy crisis, companies have had to adapt to changing environments both internally and externally. The ability to respond quickly to these challenges has become a defining characteristic of successful businesses. We recently partnered with Aiven to explore how digital native companies have evolved their data management practices in response to these challenges. The “2023 state of data management solutions for digital natives” report offers insights into the evolving data management landscape and the strategies used by companies to thrive in today’s business world. We define “fast growth” as the approach of adapting quickly to change and innovating, which is crucial for companies that want to expand. The data presented are based on a Q3 2022 survey of nearly 500 IT professionals at digital native companies worldwide. What was happening in the past? Firstly we’ll see which systems companies stopped using and which ones they plan to use in the future. We found that when adopting a new data management solution, professionals must consider all options. Replacements occur when other products offer better benefits, not because the replaced system failed. Data model fit is crucial when choosing a product, while pricing is essential when replacing one, especially for small businesses. Large enterprises prioritize technical support. Fast-growing companies prioritize service availability and disaster recovery capabilities, with 43% prioritizing this when adopting a data management tool. Inadequate backup/snapshot functionality is a common reason for replacing a tool, with 19% of fast-growing companies citing it. Conservative-growth companies are less likely to replace tools based on this feature. While data model suitability is at the forefront of reasons for adopting data management tools, pricing is often the primary factor when it comes to finding alternative solutions. What is happening now? What our analysis shows, for now, is that fast-growing companies prefer fully-managed services, while conservative-growth companies lean towards self-managed solutions, except for search technologies. Interesting highlights: On average, companies with an eye for scaling up are 16% more likely to use fully-managed services and are highly focused on search technologies and event streaming/message queue systems. Faster-growing companies tend to be more likely to adopt open-source search technologies, with OpenSearch emerging as the most popular search technology among them. 43% of those who work for companies with fast-growth business models prioritise service availability and disaster recovery capabilities when adopting data management products. What does the future of management systems look like? 56% of respondents are looking to adopt at least one new system in the near future. Relational databases currently have the lead in adoption (78% of respondents), but the demand for streaming data is increasing with the reliance on artificial intelligence, and event streaming and message queues are on track to become the second most popular data management system type among digital native companies. In terms of fully-managed services, security and performance are the most likely features to grow in importance, while pricing and cost optimization are the least likely. Fast-growing companies are more likely to adopt open-source data management products, while conservative growth counterparts are more concerned with scalability. Sustainable practices are becoming more important when selecting a DBaaS vendor, with a higher likelihood of prioritizing reducing environmental footprint over-optimizing costs. Adoption of data management tools? We dedicated a special section of our report to measure adoption. We look at 9 data management tool categories and see what % of the respondents are currently using or planning to use each data management system type. Does this align with your goals? Download the full free report to access all insights here. A word from Aiven Aiven’s cloud data platform helps your business reach its highest potential by making your data work for you. It provides fully managed open-source data infrastructure on all major clouds, helping developers focus on what they do best: innovate and create without worrying about the limitations of technology. We like to think that Aiven is not only a cloud data platform but also an extension of your team. We are dedicated to helping you to succeed by removing barriers and finding the right solutions – with the help of the best data technology there is. About SlashData SlashData has been surveying developers for more than 17 years. We talk to 30,000+ developers globally, on an annual basis. Leading tech brands rely on our insights for their developer-facing strategy. Leverage the rich data and our deep insights to segment, grow and engage your developer community by addressing their needs – directly.

You’re familiar with at least one AI-assisted development tool; That’s right, the ChatGPT. Its popularity has skyrocketed in the last few months and with good reason. It is designed to assist users in generating human-like text but it’s been helpful to developers too, as they can leverage ChatGPT to automate certain tasks, generate code snippets, assist in writing documentation, or even prototype conversational interfaces. While ChatGPT is primarily a language model, it can be used in the development process to aid in various aspects of software development. In our 24th edition of State of Developer Nation, we asked developers if they use AI and how. This led to a dedicated chapter on all the new technologies that captivate developers’ imaginations. The data from our survey suggest that 63% of developers engaged in some aspect of AI-assisted development, making it evident that this technology is rapidly maturing and transforming from a mere trend to a valuable tool. AI-Assisted Development: A Growing Trend While overall engagement has experienced a slight decline of 4% over the past year, the nature of developer involvement has undergone a fascinating shift. More developers are actively working on or learning about AI-assisted development, showing a 6% increase in engagement. Simultaneously, the number of developers with latent interest has decreased by 6%. This dynamic suggests that AI-assisted development is maturing and gaining practical applicability in the development landscape. Generative AI: Unleashing Creative Possibilities Alongside AI-assisted development, generative AI has emerged as a new and exciting technology. With 57% of developers actively involved or interested in generative AI, curiosity and excitement abound. While AI-assisted development still leads in adoption at 17%, generative AI projects attract 14% of engaged developers. The Many Uses of Generative AI Developers use generative AI in three main ways: as a helpful tool for their development process by integrating it into projects through APIs or even by creating the models themselves. Ongoing investigations are exploring these usage patterns to uncover more insights into this groundbreaking technology. Challenges and Opportunities Although generative AI is gaining high engagement, there are factors that affect its adoption among developers. Some developers may be hesitant to rely solely on generative models for critical or security-conscious tasks. However, there is a growing adoption of generative AI for visual assets in software development, which reduces the risks of errors and security vulnerabilities. Overcoming Challenges Developers who work on generative AI models face the challenge of needing a large amount of training data. However, certain tools offer the ability to fine-tune pre-trained models for specific tasks, making this challenge easier to overcome. As developers become more familiar with assistive and generative AI technologies, we can expect a surge in their adoption, leading to innovation and creativity. Leadership’s Role Interestingly, leaders in C-suite and other leadership positions show higher engagement rates with emerging technologies. About 49% and 50% of those who approve tool expenses or budgets are actively involved in AI-assisted development. This trend suggests that the revolution in AI-assisted development is driven by leaders who recognize its potential. Looking Ahead: The Changing Landscape: When we take a broader view, we see a cyclical pattern in the adoption and interest in emerging technologies. Developer interest has dropped by 5% overall, while adoption has increased by 4 percentage points. This contrast indicates a dynamic shift in developer preferences, marking a change from previous trends. In summary, AI-assisted development is rapidly evolving and attracting developers’ attention. Generative AI opens up exciting possibilities, and leadership engagement plays a crucial role in driving its growth. Cryptocurrencies continue to be intriguing, and the landscape of emerging technologies is constantly shifting. Did you find this article interesting? Download the full free report to learn about: The rest of the technologies that capture the developers’ imagination The Role of female coders in software development An update on language communities How well-paid developers feel What makes a high-quality API An Overview of embedded software development

Security threats in software development evolve at lightning speed in today’s digital age. With the average cost of a security breach in a hybrid cloud environment hovering at a staggering $3.6 million, it’s crucial for organisations to prioritize software security. This is why we recently partnered with Cisco; to uncover developers’ exposure to API security exploits, their outlook on security, and how they use automation tools to detect and remediate threats. We did so by exploring the findings from two global surveys that targeted enterprise developers and created the “Developers and Shift-Left Security” public report. How is our report unravelling? 1. Security is a key priority for enterprise developers Security threats are on the rise, with our survey data proving it; in fact, a whopping 58% of enterprise developers have had to tackle at least one API exploit in the past year alone. And to make matters worse, nearly half of them have experienced multiple API exploits during that time. As modern applications increasingly rely on microservices, securing the APIs that connect these services becomes even more crucial. But with developers juggling multiple APIs, it can be a challenge to stay on top of security. That’s why it’s essential to prioritise security from the very beginning of development to avoid wasting time and effort on reworking code and dealing with exploits later on. When it comes to security breaches, it’s best to prevent them altogether. But if they do occur, organizations must be prepared to act quickly. Shockingly, our survey found that only one-third of enterprise developers can resolve API exploits within one day of a breach occurring. By treating security as a top priority from the start of the development lifecycle, organizations can increase preparedness and avoid costly mistakes down the road. 2. How do enterprise developers address security? The philosophy behind shift-left security is all about putting security at the forefront right from the start. It’s like having a VIP seat reserved for security at the decision-making table! By addressing security concerns early on in the development process, you can save a ton of money compared to dealing with security issues during deployment or after a security breach. In fact, our data shows that many organizations are already investing significant effort in identifying security vulnerabilities during the early stages of development, and as a result, have implemented additional security measures. When do enterprise developers address security? 3. Automation makes things faster and less error-prone than manual operations. We asked developers whether they use automated approaches to security, such as scanning tools or automated fixes. The most likely group of developers to adopt automated security approaches are key decision-makers and team leads who influence, manage, or set the strategy for their teams’ purchase initiatives (90%). This means that many developers still don’t use automation tools for security. However, it’s crucial for developers to use the best tools available to ensure they produce secure code. In conclusion, APIs are crucial for modern software systems, but security exploits are a common occurrence. A shift-left approach is vital for enhancing application security from the earliest stages of development. While more than half of enterprise developers are already shifting left, less experienced developers are lagging behind. To support this approach, automation is essential, with two-thirds of developers using automated security tools. However, developers motivated by gaining experience are less likely to use automation, so organizations need to balance the need for learning with the importance of using the best security tools available. Interested in the full data and graphs? Download the full report for free.

Software is officially everywhere. Today, no matter what we do, we work in a tech business. We’ve been expecting this for a long time now. In fact, we bet our business on it. Developers, developers, developers 2000 Before developers were coined the new kingmakers, before CEOs pointed out all companies are tech companies; SlashData was tracking software developers and trends. Nearly two decades ago, we believed developers were designing the world we were moving quickly to become. Since then, the world has changed more than a few times. Leading to the irony of the newest trend. Our daily feeds are flooded by 2 contradictory highlights: Learning how ChatGPT and AI software like it makes our lives and jobs easier Mass tech layoffs Well, with every challenge comes opportunity, and we decided to take a step back and find our clarity, to see our vision once again. Up till now we have been proud to say SlashData helps the world understand developers and developers understand the world, but why? What is the value we create as a result? A value-first approach We started asking – What is the core of our business? What is the reason for our existence in the vast universe of 0s and 1s? Understanding Developers is still our core. Quite simply, it’s what we do. We help technology companies, all companies, across industries, understand developers in order to make the right investment decisions. Know your customer, know your user and don’t forget – know your non-user. Then, data is still in our DNA – as it should be. How can you make decisions confidently otherwise? Intuition isn’t cutting it. Let’s face it, maybe we are in the position we are today, because too many people make major investment decisions based on hunches and assumptions. This is why SlashData is so critical to the way businesses should make decisions. Now more than ever, investment decisions must be supported by data. Decision making backed by data is the only way to optimise spending, create efficiencies and keep jobs. Lastly, once you get down to the core of what we do – we listen to the market. We listen to developers. Tools, products, and solutions must be reactively built. If you’re not addressing a need, you are creating a solution for no one’s problem. Listening to developers, hearing their needs, preferences and whys, and then reacting to it is how you do that. Mission to the future This is how we will empower developers to code the future. Our vision is to give a voice to the developers that is amplified and spread to the world’s largest companies to help them make the right decisions, spend less on mistakes, and effectively, (dare I say it?) make the world a better place.  Here’s what will map our next steps  Vision – Empowering developers to code the futureMission – Understand developers. Inspire the future of technology SlashData’s Mission and Vision 2023-onwards We have the data, it’s now your turn to listen to it and Inspire the future of technology as a result. *Drops mic* Moschoula Kramvousanou is the CEO of SlashData. #business #softwareatetheworld #businessstrategy #missionandvision #datadrivendecisions #strategy #developers

Have you tried NGINX? Have you worked with a web server or reverse proxy? For those who have been living under a rock, NGINX is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache. It is also free and open-source software, released under the terms of the 2-clause BSD license in 2004. Last year, we collaborated with F5 NGINX to explore their community. We designed a survey that ran between August and September 2022 with more than 2,000 respondents worldwide. We took the survey findings and published the “NGINX State of App and API Delivery Report“. In this report we conduct an in-depth exploration of the following: Profile of NGINX users. We provide an overview of the survey respondents’ profiles in terms of their geographic location, role, and size of their organization, while also focusing on their use cases and the challenges they face in application (app) and API delivery projects. What did we discover? 31% of all development roles also identify with leadership roles 44% of employees at large enterprises have nothing to do with security compared to 29% and 27% for those working at medium-sized and small businesses, respectively The largest issue faced by the NGINX community is a lack of technical skills. When it comes to app and API delivery use cases respondents are working on, we find that nearly 50% are currently using web servers, 36% reverse proxies, and 34% load balancer Organisational approaches to APIs and the importance of App/API features. We then dive deeper into apps and APIs, by examining the degree to which organizations are adopting four key API first practices: leveraging APIs as sources of revenue, designing the API first when building services, aligning APIs to their overall digital strategy, And designing APIs to be reusable. Furthermore, we examine how these practices vary across company size. We also explore how important security, scalability, and observability features are in app and API delivery projects. One interesting highlight: A higher share of those with no security responsibility recognises that user authentication and authorization are very important, compared to those who build security features into their apps. Technology choices and development environments. Moving forward, we look at the technology choices and development environments of NGINX community members, with a focus on their workloads, Kubernetes adoption/maturity, where their code is run, and attitudes towards open source software. We examine how role and organization size affects each of these topics, and compare the profiles of those with low and very high workloads. Some interesting findings in this chapter include: 77% of the respondents who use a container orchestration tool are using a Kubernetes-based one. Scalability is the number one motivation for Kubernetes adoption The top 3 code deployment environments are public cloud, web client/front-end, and on-premises servers. Management, security, and monitoring/observability tool usage. Finally, we take a look at which management/security and monitoring/observability tools the community uses, discuss cross-usage, and explore the differences between the profiles of those who use NGINX and those who don’t. Among other things, we found that: Those in SecOps roles strongly favour 3 tools in particular: Google (excluding Firebase), SecureAuth, and Duo. 44% of respondents are currently working on authentication or authorization use cases Those in Leadership roles are more likely to depend solely on NGINX configuration management tool. Make sure to download the complete report to find out more on the importance of App/API features as well as on the usage on monitoring, security and management tools Interested in finding out more about your community? Let’s talk #community #developerdata #webserver #INGINX #proxy

Developer Program Leaders survey is now live! Have your say and access more results like the ones in this article. If you have been following Developer Relations and Marketing for a while, you might have noticed how the community is becoming a more and more integral part of all strategic activities. Developer Relations is becoming (if not already) a community-led effort. There is a huge benefit to any vendor to maintain a community for all the reasons that data shows us. If we can enable developers get more out of a product, if we can enable them to be excited about the product, share their experience with their peers and also progress through the community member’s lifescycle from new joiner to expert, we are helping them progress in their career and we’re also getting them more invested in our product and ecosystem. If you keep those core needs in mind, that’s when vendor communities start to add value. Jamie Langskov, Community and change management strategist. Naturally, this leaves us asking: Where do communities fit in the perception of developers? Why are developers joining communities? How are developer-facing professionals address developers’ community needs? We don’t have to guess these answers. We just need to look at the data Jamie is referring to. These data come from 2 surveys run by SlashData: the Developer Nation survey (developer-focused) and the Developer Program Leaders survey (DevRel-focused). Let’s look together at the insights these bring us.  Where do communities fit in the perception of developers? Developers join communities to learn. According to the Q3 2022 Developer Nation survey, which surveyed 23,790+ developers, 19% of developers rank community in the top 5 resources that companies should offer to support developers. This makes the community 7th most important resource overall, just ahead of answers in public forums and only slightly behind professional certifications. Student developers’ professional aspirations Having understood what makes developers join a community, we look at what the “next generation of developers” aka developers who are currently identifying as “students” look forward to. When asked about their top career aspirations, student developers (sample size of 4,790+) listed these as their top 3 aspirations: Solve problems Become an expert in a domain or technology Build innovative products/services You can see their full responses in the graph below. What the answers to this question show is how the community can be the place where student developers’ needs are getting addressed. The community can provide the space, the resources and the interactions that can help student developers meet with their top aspirations: solve problems and gain expertise in a domain or technology. Are organisations paying attention to developers’ community needs? Yes, they are. And we will data-back this affirmation by looking at the data from the latest Developer Program Leaders survey, where we surveyed ~130 industry professionals in developer-facing roles. The data speaks for itself. Communities are now sharing the spotlight with other traditional popular methods of developer education. And developer-facing organisations are aware. According to their responses, when the professionals are setting their strategy on how to talk to developers and address their technical audience needs, 73% consider community as (at least) a key part of their strategy. More specifically 34% consider community as the most important part of their strategy 39% consider community as a key part of their strategy Only 6% do not include the community in their strategy. You can see all responses at this graph: What are developer program leaders’ roles? By now we have established the importance of community in a developer marketing strategy. To better understand how this strategy is implemented, we will look at the hats these developer program professionals are wearing to implement this strategy and we will also look at the community sizes – for perspective. With 73% of those professionals reporting community as a key part of their strategy, it comes as no surprise that 34% of them have “Community Manager” as their professional title, the second most popular, right behind “Developer Relations Practitioner” and only slightly above “Developer Marketing Practitioner”. “I’ll have one ‘large community, please” Communities come in different sizes. While everyone strives to build a space with a massive, always active user base, the reality sometimes shows differently. In fact, only 4% of the Developer Program Leaders reported running an active community that counts more than 10M members. 27% responded to running communities smaller than 100 members. The less people are in a community, the more effort is needed to keep the discussion going. Which begs the question: how can you engage the community members? Driving participation in the community To answer this question, we don’t look at what community managers are doing to increase engagement in their communities. We ask developers what makes a community fun for them. 33% of developers (sample size 10,478) responded that having a well-designed community platform is their #1 reason that encourages them to participate. Four more reasons are tied for the second place, with 29% of respondents saying that what encourages them to be active are: Getting regular updates Fun activities A well-defined purpose for the community Projects on which community members can work together The latter one is especially important for students. Here is the full breakdown of their responses: Developer community + DevRel strategy wrap up In summary, looking at the latest data from our Developer Nation survey (developer-focused) and the Developer Program Leaders survey (DevRel-focused) we reach the following conclusions which we discussed in this hopefully-not-that-long article: Developers rank community at their top-5 resources Developers’ #1 reason for joining communities is training and resources A community can be the means to address student developers’ top aspirations Community is considered a key part of a developer-facing strategy by more than ⅔ of developer program leaders Community management is the second most popular title Communities come in all shapes, but even more sizes Developers share what makes them engage in a community and are happy to share it. How are you addressing your developer community? Join the discussions with like minded people at the DevRelX community . If you want more data on developer needs and wants or you are trying to better understand developers, SlashData has the insights you need.

It’s the most wonderful time of the year! Yes, the beginning of the “Merry” season but also the time when new insights from the world of developers come to everyone’s house (magic may or may not be involved)! Stay up to date with the 23rd edition of the State of the Developer Nation report and get the insights you would only pick up by slashing through data with your own two hands. Our 23rd Developer Nation global survey reached more than 26,000 developers in 160+ countries and its findings are bundled in a free “State of the Developer Nation” report. This research report delves into key developer trends for Q3 2022: The state of blockchain development Students’ top career aspirations Language communities – An update Why developers contribute to vendor-owned open-source projects Types of studios game developers work for The rise and fall of web frameworks In addition to outlining the report’s major findings, here are a few key takeaway points to spark your curiosity: The state of blockchain development 25% of developers are currently working on or learning about blockchain applications other than cryptocurrencies. Developers with 6-10 years of experience in software development are the most likely to be working on blockchain projects. Though Ethereum is the dominant blockchain platform, it is the only one more popular among learners than those currently working on blockchain applications. Language communities – An update Javascript remains the largest programming language community, with an estimated 19.6M developers worldwide using it. In the last two years, Java has almost doubled the size of its community, from 8.3M to 16.5M. For perspective, the global developer population grew about half as fast over the same period. Kotlin and Rust are the two fastest-growing language communities, having more than doubled in size in the past two years. The rise and fall of web frameworks Web developers who use frameworks are more likely to be high-performers in software delivery than those who don’t. Web developers are gradually settling for a smaller number of frameworks as they stop experimenting with a wide range of tools. React is currently the most widely used client-side framework and its adoption has remained stable over the past two years. By comparison, jQuery’s popularity is decreasing rapidly. As you’ll notice, most of the trends we discuss in this report are takeaways from how developers use technology. Our goal is to share these insights with the world to help guide the next generation of development. 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. #developerdata #developerresearch #developertrends

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. #casestudy

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. #developermarketing #developerrelations #developersurvey