Search Results

The developer landscape is shifting faster than ever. AI agents are moving from buzzword to reality. Cloud deployment has become universal. Security threats are multiplying alongside AI's expanding attack surface. At SlashData, we don't just track these changes; we decode what they actually mean for the companies building developer tools and platforms. For our 30th wave of Developer Nation, we're expanding our focus areas, refining our intelligence gathering, and improving our methodology to ensure our research remains the most relevant and actionable in the industry. Professionals across the full breadth of the development sector — CTOs, product and program managers, engineers and DevOps teams, and more — rely on that intelligence.  Moschoula Kramvousanou, CEO talks about our research focus for 2025 Why now? Because as the technology landscape evolves, vendors are finding it increasingly challenging to understand what their developers truly need and how they truly work. We're introducing new research areas and enhanced methodologies based on direct feedback from leading technology companies who depend on our insights to make critical product and strategy decisions. The result is our most comprehensive survey yet, designed to give you the intelligence that actually drives business outcomes. Why This Intelligence Matters Now The technology sector is experiencing its most significant shift since the mobile revolution. AI capabilities are reshaping every development workflow. Cloud infrastructure has become invisible but critical. Security requirements are evolving faster than security practices. Companies making decisions based on outdated intelligence – or worse: vendor marketing – are missing the real opportunities and risks. Our H2 2025 research cuts through the noise to deliver the insights that actually drive successful developer products and strategies. Whether you're deciding where to invest AI development resources, how to position cloud tools, or which developer segments to prioritise, this intelligence gives you the foundation for decisions that matter. Core Intelligence: AI Agents and Security Reality Check AI Agents: Cutting Through the Hype Everyone's talking about AI agents, but who's using them? We're asking over 10,000 developers worldwide about their real experience with agentic architectures. Not the marketing promises, but the ground truth. Which platforms are gaining genuine traction? What specific tasks are developers successfully automating? How well do developers understand core concepts like Model Context Protocol compared to how well vendors think they do? We're asking over 10,000 developers worldwide about their real experience with agentic architectures. Not the marketing promises, but the ground truth. This intelligence emerged from conversations with major AI platform providers who need to understand whether their educational and marketing efforts are translating into adoption and where the genuine market opportunities lie. We're also investigating developer familiarity across the full spectrum of agentic AI platforms and frameworks, providing comprehensive competitive intelligence for this rapidly evolving space. DevSecOps: The Security Gap Analysis With AI agents expanding attack surfaces and security breaches dominating headlines, we're conducting a renewed investigation into DevSecOps. We're mapping the critical gap between developers' expressed security concerns and their actual implementation practices: examining the frequency of security checks, CI/CD pipeline ownership, and the implementation of security guardrails. Previous SlashData research revealed security as a top developer concern, but practice consistently lagged behind stated urgency. Now we'll provide definitive insight on whether the industry is finally catching up, and what real-world implementations actually look like. Cloud Intelligence Trends: Beyond Backend Specialisation Universal Cloud Reality Starting H2 2025, we're surveying all cloud users: not just backend specialists. We're breaking down the artificial barriers in cloud research that have limited the breadth of understanding we can provide. For years, we limited detailed cloud questions to backend developers, but with over 90% of developers now using cloud services, that approach missed the full picture and critical insights. Starting H2 2025, we're surveying all cloud users: not just backend specialists. This expansion gives you comprehensive insight from both the developers configuring cloud tools and infrastructure and those using cloud services in their daily development work. The difference in perspectives between these groups often reveals critical gaps in product positioning, user experience design, and feature prioritisation that can make or break adoption strategies. Cloud-Native Deep Dive We've significantly expanded our cloud-native development tracking to capture the real adoption patterns and preferences across emerging technologies and methodologies. With our survey scale spanning thousands of backend developers, you'll get unprecedented visibility into which cloud-native approaches are actually driving adoption versus which ones are generating buzz without substance.  Data Residency and CSP Intelligence We're also introducing comprehensive tracking of data residency compliance requirements and how they influence cloud deployment decisions. Combined with our enhanced cloud service provider preference analysis and expanded cloud-native research, these three focus areas reflect the growing complexity of cloud decision-making. Our CSP clients have shown particular interest in understanding how developers navigate these interconnected challenges, as regulatory requirements increasingly shape technical architecture choices. Developer Program Benchmarking: AI Integration and Sample Code SlashData's developer programme benchmarking has become a cornerstone for leading technology companies understanding where they excel and where they need to improve. For years, our benchmarking has enabled clients to directly compare their developer programmes against competitors, providing critical insights into how they fit within developers' core workflows and decision-making processes. This established expertise allows us to speak with authority about industry-wide trends and pain points. AI Assistant Integration Building on our benchmarking foundation, we're now tracking the integration of AI assistants and tools as a core programme feature. The largest companies in our network are aggressively pursuing these capabilities, but questions remain: How important is this to developers? Which developer segments care most? Our expanded benchmarking will give you clarity on where to invest your AI support efforts and how to position these against competitor offerings. Sample Code: The Industry's Biggest Failure Point Our extensive benchmarking work has consistently revealed that vendor-supplied sample code is where the entire industry falls short of developer expectations. This wave, we're conducting our most comprehensive sample code analysis yet. We’re examining what features developers actually value, their biggest frustrations, and the specific scenarios where they turn to sample code versus other resources. We're also having developers rate familiar vendors across multiple sample code dimensions: relevance, discoverability, production applicability, and currency. Combined with our curated understanding of developer preferences and pain points, this will provide a complete picture of how sample code impacts developer adoption and satisfaction. If you're not measuring up, you won’t know exactly where to focus your improvements. Specialised Sector Intelligence Gaming Industry Transformation The gaming sector is navigating unprecedented change, but one thing remains constant: the quality of games continues to reach new heights. While the creative output has never been stronger, the developers and studios behind these exceptional experiences are facing significant challenges. Our upcoming State of Game Development report (coming November 2025) will provide comprehensive profiling of game developers to understand their current landscape, technology choices, and perspectives, with an additional focus on how AI tools are helping or hindering their work, adding crucial 2025 context to this analysis. We've enhanced our profiling capabilities to distinguish between technical roles, creative roles, and non-technical support staff. These are critical segmentations for companies targeting different aspects of the gaming development pipeline. This granular approach allows engine providers, tool creators, and platform companies to understand exactly which roles are most receptive to their solutions and what specific challenges each segment faces in their daily work. XR Reality Check Despite major moves like the Apple Vision Pro, XR hasn't achieved mainstream presence. Our XR Landscape report will provide updated intelligence on who's actually working in this space, plus 10-year predictions from developers across all sectors. Are XR developers more optimistic than the broader market? Do younger developers see more potential? The answers will likely shape XR investment strategies. AI at the Edge Edge computing and AI/ML are converging rapidly, creating new opportunities and challenges for developers and the companies serving them. This has become a growing topic of interest that's increasingly important to many vendors with the proliferation of small advanced models that can run effectively at the edge. We're conducting comprehensive research into which edge AI/ML projects are gaining real traction beyond proof-of-concept stages, what specific frameworks and development approaches developers prefer, and where the current pain points create the biggest opportunities for better tooling and platforms. This research covers the technical requirements and the developer experience challenges that determine success in this emerging market. IIoT Developer Journey We're also investigating how Industrial IoT developers first entered the field, focusing on their initial development board experiences and early learning journey. This research helps companies in the IIoT space understand how they stack up against competitors in terms of developer onboarding and initial experience; critical factors for long-term ecosystem adoption. That’s not all In addition to these comprehensive research areas, we offer client-exclusive questions designed around your specific intelligence requirements. This bespoke research capability ensures you're not just getting industry-wide insights, but the targeted data that directly informs your unique strategic challenges and opportunities. The 30th wave of Developer Nation is currently collecting responses from around the world. If you want to help shape these insights, have your say .  You can be the first to know when these insights become available by subscribing to our newsletter . Or you can get in touch  and we will make sure to get you all the intelligence you need.  About the author Liam Bollman-Dodd, Senior Market Reseach Analyst Liam is a former experimental antimatter physicist, and he obtained a PhD in Physics while working at CERN. He is interested in the changing landscape of cloud development, cybersecurity, and the relationship between technological developments and their impact on society.

Or what skills are you focusing on improving? This is a post from DevRelX. DevRelX was a community-driven platform by SlashData dedicated to advancing Developer Relations (DevRel), Developer Marketing, and Developer Experience professionals. It provided research, insights, and resources through initiatives like the Future Developer Summit & the DevRelX Summit, the DevRelX Podcast, and a book. DevRelX created a vibrant space for learning, connection, and discussion within the global DevRel community, until the community was sunset in 2023 as SlashData shifted its focs to wide Technology Research. The DevRelX Community Voice column is one of a few ways we invite our community members to share ideas and solve challenges around various topics like DevRel strategy, metrics, career growth, and just DevRel’s day-to-day. Want to add your voice to this and more key DevRel topics? Join our community and participate in the next Community Voice prompts where you can ask your questions! Opemipo Disu, Developer Advocate at Fermyon I think communication is a skill an aspiring DevRel should have DevRel acts as a 'middle-man' between the company and the users. In a DevRel role, it's essential you get across to users' feedback and in this case, I think communication is pretty much important in this case. Pj Metz, Developer Community Manager #OpenToWork Empathy and authenticity. Developers don’t like to be marketed to, so making sure that you’re being yourself and understanding what it is that they need from a DevRel is very important. Developers have problems to solve, and DevRel has a possible solution. That’s the goal is to show them the problem being solved, not making promises about speed, agility, etc. Show the problem getting solved. Tabatha DiDomenico, OSS Developer Relations & Security Advocate Listening is a skill that deserves attention or, really, listening with intention —engaging with a goal in mind more often yields actionable, helpful ideas. Of course, the casual conversation has its place, but it may take a while to discover valuable insight for both parties. Even taking a few seconds at the start of a conversation to anchor to a context can help make the most of each connection. Sean Falconer, Head of Marketing & Developer Relations at Skyflow I think it's a bit context-dependent. You need to do a bit of self-analysis and figure out where your weak points are and proactively try to work on those things. If someone is highly technical but has less experience presenting and/or writing, then you should try to build up those skills. If presenting and engaging with people comes naturally but you have the less technical skill, then focusing on deepening your technical skills makes sense. Working in developer relations, especially advocacy, requires a wide breadth of skills. To be really good at it, you need to constantly be working on skill stacking: listening, writing, speaking, programming, and explaining technical concepts to different types of audiences are all skills that you need to be building. So my long-winded advice is to try to shore up your weaknesses. This is also great for storytelling in an interview, it shows you care about self-improvement, you have passion for what you do, and even if you don't perfectly line up with the job requirements, you're someone who's going to walk through walls to level up so you can do the job. Michael Arguin, Senior Manager, Marketplace & Developer Experience Curiosity and a passion for learning . You won't know everything so you will often have to find answers. Jason St-Cyr, Developer Relations leader at Sitecore A key piece for me is the ability to learn and then teach . In many situations, you need to be encountering something new before others, learn that to keep ahead of the need, and then be able to create something that helps others learn what you just had to. Katie Miller, Director, Developer Marketing Slack Cross-functional relationship building , which encompasses flexibility, curiosity, empathy, and how to reframe communication style and methods to meet folks where they're at!

This is a post from DevRelX. DevRelX was a community-driven platform by SlashData dedicated to advancing Developer Relations (DevRel), Developer Marketing, and Developer Experience professionals. It provided research, insights, and resources through initiatives like the Future Developer Summit & the DevRelX Summit, the DevRelX Podcast, and a book. DevRelX created a vibrant space for learning, connection, and discussion within the global DevRel community, until the community was sunset in 2023 as SlashData shifted its focs to wide Technology Research. The start of 2023 marked a 3-year anniversary of DevRelX.com - thank you for being with us! Another Q1 highlight in our community is the 10th Developer Program Leaders survey , a bi-annual effort to understand your and your peers' challenges, and how DevRel professionals prioritise resources and justify the value of their developer program. We invite you to participate and gain access to insights into how you compare against peer practices and contribute to the industry’s knowledge share. Interested? You’ll need ±8 minutes. Take the survey For every complete response, we will donate $3 (and up to $500) on behalf of the DevRelX Community to support the people who have suffered from the devastating earthquake in Turkey and Syria . Now, let’s take a look at some of the key findings from our past surveys, complemented by expert insights from our members! Building a Developer Program Strategy Sean Falconer shared personal thoughts on Q4, 2021 survey insights. Below are some of the highlights and you can read more in this blog post . How do program leaders spend their time, budget and effort? Below are the results from the survey breaking down how developer program leaders spend the majority of their time. It’s encouraging to see that program leaders are spending the majority of their time on strategy. As Benjamin Franklin famously said, “ Failing to prepare, you are preparing to fail. “ When I joined Skyflow , I spent a lot of time immersing myself in the product, the problem space, meeting people and customers, and thinking deeply about strategy. I wanted to be able to put together a long-term vision. What does developer relations look like for Skyflow in 5 years? And, a short-term vision. Where will it be in 6 months? Starting with a strategy and creating a plan helped me focus on where I should put my attention and how to think about hiring. There are always a million things to do at a startup, but if you try to do everything at once, you’ll do nothing well. A strategy with clear objectives helps you tune out the distractions and focus on moving your key metrics in the right direction. Thinking about and creating a strategy should be the foundation of any developer program. You should outline your goals, and the things you’re going to measure, define a North Star metric, and plan the tactics that will get you there. However, just because you have a plan doesn’t mean it’s going to work. As Mike Tyson said, “ Everyone has a plan until they get punched in the mouth. “ You need to be able to adapt. Failure is to be expected. It’s a learning opportunity. Just don’t make the same mistake over and over again. Internal buy-in and funding The survey reports that 22% of a leader’s time is spent creating internal buy-in or securing funding. In a prior survey , this was 15%. I think part of the responsibility of any program lead, regardless of function, is to spend some time justifying their function’s existence and securing funding. It’s our responsibility to convey our program and team’s value. That being said, I think it’s unfortunately too common that developer program leaders spend A LOT of time on this and it’s a topic that continually comes up. At Google, I felt that several times a year, I had to give presentations explaining what my team did, the value we brought to the program, and the impact we’d had, but even then, I really had to fight for resourcing. Continually fighting this battle is counterproductive and exhausting. So although it’s part of a program lead’s responsibility, I believe there should be a limit. Ultimately, it’s critical that developer programs have executive buy-in and are seen as a strategically important investment. Without that, you’ll burn yourself out trying to make people understand something they are simply not ready or interested in accepting. Understanding where you are and where you need to go Ayan Pahwa has also highlighted the importance of internal buy-in when looking at the Q2, 2022 results in this blog post . Here's what he shared: Internal buy-ins and getting funding: Steadily bridging the gap Now, this is an interesting one. Seeing a drop in creating internal buy-ins and securing funding from 22% in the Q4-2021 survey to 15% this year, really proves that DevRel practitioners are now spending relatively less time in convincing and justifying the cost of their DevRel programs. This could be the result of developer advocacy programs becoming more mature and clearly linked to strategic goals. The impact of developer advocacy programs and their integration into company-wide strategy seems to be making it clearer for stakeholders to consciously invest both budget and resources in DevRel efforts. I’ve been on the spot, spending hours to justify the cost of attending a conference or organising an event or just buying a new service or platform subscription to support our Developer community, so it’s really good to see that time is being claimed back and spent doing other rather more impactful tasks such as : Direct developer engagement (rising from 11% to 18% ). This is one of my favourite activities as a developer advocate. The feedback you get during 1:1 or 1:many interactions is extremely useful and specific. This also gives you an opportunity to create relationships on a much more personal level with members of your developer community, which can later become the foundation of your ambassador program . Understanding of the product: Although not showing up in the results but of great importance based on personal experience, is time spent in understanding your own product better. This is especially true for developer-first organisations where the products are ever-evolving and getting complex.s a DevRel practitioner it’s important to stay up-to-date with your own product growth and for someone who just joined a new organisation as DevRel, quite a significant amount of time can go into learning about the product itself. Challenges calculating on-boarded developer value: The survey also asked how a Developer program budget is justified and the estimated lifetime value of an on-boarded developer. It’s clear that the majority of people (~45%) participating in the survey don’t have a solid methodology for calculating the value of an on-boarded developer and hence only a small portion (8%) has backed the budget allocated to the developer program by an exact FIAT value. Given the complex developer lifecycle and pricing plans of developer-facing - products, platforms and solutions, it’s fairly complicated to create a solid framework that can help calculate the exact dollar value associated with an on-boarded developer. Most products often have a free tier associated up to a certain usage and some also have free tiers for certain segments of developers such as student groups or non-profits. A developer can also evolve from being a part of a free tier to onto a paying payment plan over time and hence adding more complexity to put a dollar value on developer acquisition. It’s also difficult to know which acquisition strategy exactly works in onboarding a new developer, whether it’s that Youtube video you recently published or a past conference talk or demo during a local meet-up, It could very well be your SDK written in Go with good documentation. How companies and DevRel serve the communities developers join As we continue following Developer Relations and Marketing field, we notice 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. With that in mind, our most recent survey (Q4, 2022) , zoomed into the following: Where do communities fit in the perception of developers? Why are developers joining communities? How are developer-facing professionals address developers’ community needs? Where do communities fit in the perception of developers? Developers join communities to learn. According to the Q3 2022 Developer Nation study , 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. 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 in this graph: Have you enjoyed these insights? Respond to the survey before March 31 to gain access to more insights like these and a chance to win exclusive DevRelX swag - Have your say !

This is a post from DevRelX. DevRelX was a community-driven platform by SlashData dedicated to advancing Developer Relations (DevRel), Developer Marketing, and Developer Experience professionals. It provided research, insights, and resources through initiatives like the Future Developer Summit & the DevRelX Summit, the DevRelX Podcast, and a book. DevRelX created a vibrant space for learning, connection, and discussion within the global DevRel community, until the community was sunset in 2023 as SlashData shifted its focs to wide Technology Research. As the demand for developers continues to grow, so does the need for great developer relations (DevRel) professionals. Companies are looking for individuals who have strong communication and interpersonal skills, as well as a deep understanding of various coding languages. Not only must these DevRel candidates possess technical aptitude, but they should also be problem-solvers with excellent time management abilities and even customer service experience. In this article, we will discuss what employers look for when hiring DevRel professionals and provide tips on how to gain the necessary experience. What Is DevRel And Why Is It Important? Before we dive into the skills, let's define DevRel as a career path. DevRel stands for Developer Relations and is often referred to as: Developer Advocacy Developer Evangelism Developer Marketing Technical Evangelism It’s a role within the software engineering industry that bridges the gap between developers and the company they work for. DevRel professionals act as liaisons, providing technical guidance while also advocating on behalf of their company by representing its products and services to the dev community. The goal of DevRel is to create a connection between developers and their employers, allowing companies to gain insights from their dev audience and providing devs with the resources they need to do their job more effectively. This helps companies increase customer loyalty, build better relationships with their dev communities, and improve brand perception overall. Qualities Employers Look For In DevRel Candidates In general, from what we have seen across our job board DevRel Careers , there is a specific set of skills that is important for prospective candidates to have and there seems to be a repeating pattern of the below skills: Technical Skills "Do I have to code?" is a common question I have heard from younger aspiring DevRel candidates and although not essential in every role, it draws down to how well you will be able to understand your developer community. Often times their problems are complex and it's almost impossible to understand without knowing at least the basics of a specific coding language. This is also the reason why many successful DevRel professionals were devs before. With a plethora of coding languages, you might be wondering which ones should be the first ones to learn, and this totally depends on the companies you are applying for. There are jobs like the recent DevRel Lead position at Fluence Labs , or the Developer Advocate role at Anvil , that are pretty technical and require proficiency in some coding languages like JavaScript, Typescript, Rust, or Python. Then, there are blockchain companies such as ConsenSys , Ava Labs , Aptos , and Kava Labs that require you to have knowledge of Ethereum, layer 1 blockchain networks and crypto in general. However, there are also less-code-heavy opportunities available, mostly within roles that are more inclined towards Community Management , Product Marketing or Developer Marketing , and require more interpersonal and marketing skills rather than coding. Within those roles, at least a minimal knowledge of coding is still beneficial though. The top coding languages that come up most frequently on our job board DevRel Careers are JavaScript, Python, Java, and TypeScript. Knowledge and experience in using APIs and SDKs are also popular requirements by employers. In conclusion, without any technical skills, it will be hard to climb the ladder of Developer Relations, and if this is the case, perhaps it's worth asking yourself if it's really what you want to pursue. After all, Developer Relations is all about being passionate about the technical solutions you are promoting and advocating for. Communication Communication, either written or verbal, is an essential skill for DevRel professionals. After all, their job is to build relationships and facilitate dialogue between developers and the company they represent. To do this effectively, DevRel professionals must be able to convey ideas in a clear and concise manner so that the dev community can understand them. For example, a recent Developer Relations open position at Netlifly states that This job requires not just understanding things but explaining them in a way that brings others along with you and inspires them to follow your lead. Public Speaking The ability to share technical knowledge and demonstrate product features in a confident and comfortable manner is essential for successful DevRel candidates. Public speaking engagements can take many forms, from presenting at conferences and webinars to giving product demonstrations or leading workshops. A recent DevRel Engineer position at LibLab requires candidates to be comfortable with public speaking and representing the company in developer communities while Discord requires applicants to have confidence presenting to different types of audiences, large and small, virtual and in-person. So, developing and practising your public speaking skills can be a great way to demonstrate your DevRel capabilities and make yourself more appealing to potential employers. Empathy Personally, I am very indecisive about whether empathy is a skill that can be learned or a natural talent. Being a mixture of patience and a deep understanding of the person you are communicating with, empathy is a quality that comes up in almost every developer relations job listing. And it's not surprising, because empathy helps DevRel professionals better understand their dev audience and anticipate their needs. In addition to having technical knowledge of the products and services they represent, DevRel professionals are expected to establish a human connection with developers by listening to their feedback and adapting to their needs. For example, a Head of Developer Relations position at Ably states that You will be successful if you empathize with the challenges developers face, and are excited by the prospect of reducing complexity for developers. Problem-Solving Problem-solving skills are key for DevRel professionals, as they need to quickly and effectively spot potential challenges and develop solutions. Problem-solving requires the ability to think critically in order to evaluate challenges from different angles and come up with creative ideas to solve them. Recruiters also look for DevRel professionals who are persistent and can work through problems independently. As stated in the DevRel and Marketing job listing at Packt , the ideal candidate should be "comfortable using a combination of intuition, experience, and expertise to identify potential problems and can take corrective action quickly”. This is where your technical experience can come in handy, as most developers are problem-solvers and have experience troubleshooting complex issues. Time Management Time management is also a highly sought-after skill for DevRel professionals. This role requires a certain level of organization and discipline to manage multiple tasks, projects, and deadlines. As DevRel professionals often have a large variety of responsibilities ranging from content creation to writing code to attending conferences, it's important to know how to fit everything into the limited amount of time. Customer Service Developers expect DevRel professionals to provide them with thoughtful and personalized support. From helping developers understand product features to troubleshooting technical issues, DevRel professionals must be able to work collaboratively with the dev community in order to ensure their success. For example, DevRel engineers at GitHub are expected to provide world-class customer service and support . A recent Senior Developer Relations opening at Audiomob states that the selected candidate will be guiding clients through the plugin integration process and championing their needs. Why Is Previous DevRel Experience Important There are companies like Matter Labs or Okta that already have a Developer Relations team and their work structure in place. However, many companies are only starting to put together a DevRel department and most are looking for their first DevRel hire . Someone who will be in charge of responsibilities like: Establishing operational procedures and standards for developer relations Building a community of advocates and champions for the company's software Creating an online content strategy Creating a strategy around events, webinars, and speaking opportunities Identifying opportunities for partnerships So, getting into a role with no actual experience is definitely risky for the employer which is why most DevRel open positions require you to have some. Having a background in DevRel shows recruiters that you understand the role and have proven yourself capable of performing it. Gaining Skills & Experience Gaining the necessary experience in order to apply for jobs in DevRel might look slightly different depending on whether your aim is to achieve a role in a more technical direction (developer documentation, developer support) or in a marketing-related role (developer marketing, community management). If you are someone with technical background , i.e a developer, and are thinking about switching your career to developer relations, then you might think about using some of the below ways to showcase your experience: Share your knowledge: Start writing, recording tutorials, or speaking about the software you use. Take on some DevRel responsibilities at your current position: There may be a need for DevRel activities at your company that you are not aware of. Talk to your employer and see whether, for example, creating content for the company could be needed. If you are someone without a technical background , i.e a marketing professional, and are thinking about transferring to a Developer Marketing role, consider gaining experience with the following: Research the differences between general marketing and marketing to developers: Create a report/presentation/video of your findings and share this with potential employers. Learn the basics of coding: There are lots of courses and bootcamps available online for acquiring some knowledge of the main coding languages. Final Thoughts To sum up, Developer Relations seems to be one of the most versatile career paths and it is an increasingly important role in the tech industry. Companies are looking for candidates with strong technical and interpersonal skills, one of the most important qualities being empathy. Whether you have a technical background or not there are ways to gain the necessary DevRel experience through writing content, taking on DevRel responsibilities at your current job or learning to code and sharing your knowledge along the way. However, most importantly, it is necessary to have passion and genuine interest in the role, because, as ConsenSys has beautifully put it: While we have a pretty good idea of what we need, we're ready for you to challenge our thinking on who needs to be in this role. Hope you found this article informative and helpful. If you wish to share ideas or discuss the subject more, you can message me in the DevRelX community . To find job opportunities in Developer Relations, feel free to check out DevRel Careers where we post new jobs daily.

This is a post from DevRelX. DevRelX was a community-driven platform by SlashData dedicated to advancing Developer Relations (DevRel), Developer Marketing, and Developer Experience professionals. It provided research, insights, and resources through initiatives like the Future Developer Summit & the DevRelX Summit, the DevRelX Podcast, and a book. DevRelX created a vibrant space for learning, connection, and discussion within the global DevRel community, until the community was sunset in 2023 as SlashData shifted its focs to wide Technology Research. 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 no w? 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.

This is a post from DevRelX. DevRelX was a community-driven platform by SlashData dedicated to advancing Developer Relations (DevRel), Developer Marketing, and Developer Experience professionals. It provided research, insights, and resources through initiatives like the Future Developer Summit & the DevRelX Summit, the DevRelX Podcast, and a book. DevRelX created a vibrant space for learning, connection, and discussion within the global DevRel community, until the community was sunset in 2023 as SlashData shifted its focs to wide Technology Research. You successfully completed the company onboarding, met with key stakeholders and familiarised yourself with the necessary services and products. What’s next? The first task for every successful developer advocate is proposing and creating what is popularly known as “ DevRel Discovery ”. DevRel discovery is usually possible and brings success by adopting a series of models and frameworks. As the first on the team, the following will be the necessary first tasks in the “DevRel Discovery” process. Understanding the company and service landscape. Developer Experience Audit (DX Audit). Goal Setting In this article, we will examine what, why and how to successfully carry out DevRel Discovery focusing on the above three (3) objectives. We will talk about each element and the impact it will have on the team's development and growth. During my research process, I thought of structuring this article to resemble a case study, which is why you will see me using Company X for the company name we are representing and Company X is a developer-first company. Understanding the company and service landscape It is important to have the above tasks in order early on, and the success of the first task (understanding the company and service landscape) will depend on other teams’ understanding of the role of developer advocate. Customer supports and customer success, sales and sales engineering teams and other teams and stakeholders need a deep understanding of the role to ensure alignment across the board. Here are the actions you can take to achieve this: Internal Education : Prepare the “DevRel Playbook” document with the teams and stakeholders. This is a short and very brief document, usually not more than 15 slides. Explaining what DevRel is and what the company can expect from the developer advocate role and how this function can benefit other teams. Gather responses to examine the perspectives of members in different teams to their views and expectations towards the role of a developer advocate. Schedule interviews with stakeholders : Use the responses collected earlier and include them in your Playbook deck's. It is an excellent time to discuss where individual teams stand with their expectations for the DevRel team. It is crucial to connect all our actions to our role, as developer relations/advocates. Through this interview, you will understand the following: The goals and priorities of every stakeholder in the company Company challenges and how the DevRel team can help tackle them. Marketing model (marketing model or orbit framework etc.) Track conversion strategy by the sales and marketing team How do I measure success? At the end of the above two processes, you should be on a high level of understanding of both the company goals, services and the stakeholders. The number of successes recognised through different team strategies. The number of challenges discovered facing another team focused on the DevRel team. The number of staff or teams that understand the role of a developer advocate in relation to their teams (aim at 70% of the staff to be onboard instantly and check in on the progress over time). Developer Experience Audit (DX Audit) After the company landscape exploration, stakeholders’ interviews and learning about the nitty-gritty of the business, it is time to discover the friction log by looking into the Company X service from the developer's point of view. This process will reveal a lot about the company’s customers, and services and will help you discover how easy or hard it is for users to sign up and get on board with your product, the number of technical guidelines and documentation. The main purpose of the process is to document, report, and provide solutions to any kind of friction or inaccuracies discovered in the developer workflow and necessary feedback for service improvements. The best strategy to use at this level is to test and do a developer workflow for each of the Company X service use cases. Here are the main steps you should take to complete Developer Experience Audit: The report should focus on each use case, offering feedback on the good or bad sides of e.g. the integration into the web should (not to be assumed for integration into iOS or Android). Customer’s voice: this can be done by collecting users’ feedback sourced via social, forums, surveys and GitHub discussions. Create a ticket to follow each of the feedbacks till they are all resolved and keep track of the time taken. Build a project to test out use cases. How to measure success? The number of frictions discovered and how quickly they were resolved. Customer feedback after friction removal and their experience and satisfaction with your product. The number of new users acquired. Stakeholders, sales and marketing teams’ experience and impact on cross-team goals (identified in the next step.) Goal Setting A famous quote from Bill Copeland says: “The trouble with not having a goal is that you can spend your life running up and down the field and never score”. This applies to our work in Developer Relations too. Here a lack of S.M.A.R.T, Specific – Measurable – Attainable – Relevant – Time Bound, goals for the team will affect and bring down your results, and how fast and successful the developer advocate team will be. For every team bringing business impact and creating meaningful programs starts with having the right goals and strategies to achieve them. Among the tons of frameworks, I will focus on the Objectives and Key Results (OKRs) framework. Let’s take a look at the example of my first set of OKRs at Company X. Business Objective: Grow revenue by increasing our number of customers through community engagement Key Business Results: 1. 150 leads added to the pipeline 2. 100 existing opportunities engaged through community 3. 50 new customers acquired 4. Retain existing customers Metrics: 50 new members Focus: New and existing customers The above OKRs are what is crucial to tackling as DeRel team at Company X among other initiatives. It is important to note that these numbers will vary across different companies and it will depend on your present company’s size to base your projection of the key results and metrics for future growth. Conclusion Congratulations on reading this article to the end, you should now be ready to take on your first tasks as a developer advocate in your company especially, if you are the first one on the team and your company is developer-first focused. I hope you learnt how to set up DevRel Discovery based on three basic models which are Understanding the company and service landscape, developer experience audit (DX Audit) and Goal Setting. It is important to note the emphasis should always be on creating strategies and ways to measure success at every stage of your activities and programs. It is very important for successful developer advocates to tie their achievements to business outcomes. I hope that you found this article useful and informative. In case you have an interest in discussing this with me and peers in the community, you can reach me through the DevRelX Community . I would love to hear your feedback and can’t wait to hear if this article has helped you in your career and set you up for success as a Developer Advocate. I am Rasheed, a software developer (DevOps) passionate about community and community building. I am the lead organiser at Cloud Native Computing Foundation, Minna and a GitHub Campus Expert. You can also find me and follow my work on Twitter , Linkedin and GitHub .

This is a post from DevRelX. DevRelX was a community-driven platform by SlashData dedicated to advancing Developer Relations (DevRel), Developer Marketing, and Developer Experience professionals. It provided research, insights, and resources through initiatives like the Future Developer Summit & the DevRelX Summit, the DevRelX Podcast, and a book. DevRelX created a vibrant space for learning, connection, and discussion within the global DevRel community, until the community was sunset in 2023 as SlashData shifted its focs to wide Technology Research. What even is a DevRel? What do they do? Do they actually work? Why are they all crazy about avocados? Are there types? Let's talk about it! If you've been in the industry for a while you might've encountered the term "DevRel" followed mainly by an avocado emoji (🥑), and your next logical thought was what is even a Dev Rel?!? and let me tell you, you're not the only one. Do they even do work? Do they tweet all day? Do they just travel around? Are you tired of explaining what you do for a living? Make this article the reference guide for your close ones that have no idea why you’re always on Twitter or on video calls. Hi, I'm Yuri and I've been working on a startup as a Developer Relations Advocate (DevRel), and this is actually my first tech role after changing careers. I've crafted much of what is now my daily schedule but I'm getting ahead of myself, first let's talk about what is a DevRel? What is a DevRel? Now, you might see many people describing it differently depending on their role. Me? I'm a bit about the 3 types we'll see in the next section so I'll provide you with a broad description of what DevRels are. DevRels sit between the company (product) and the developers . They help advocate for the product and reinforce contact with the community. How? By creating content about the product, offering support for developers, recording demos, attending conferences, working on documentation, establishing onboarding processes for clients, new team members and developers, organizing events, reviewing and merging PRs, and many other activities. So yes, they do work! Just not your usual engineering role, since it doesn't only involve coding, it's about creating content and connecting with the community. Types of DevRel We can identify that we have 3 main types of DevRels, those focused on the community, those on the product and then content creators. - Community-focused DevRels: As the name implies, they focus more on creating, growing and nurturing product-based communities. One of the biggest responsibilities is to create a safe and inclusive environment where feedback and questions are not only encouraged but appreciated by the team members. How? Interacting with the members, organizing and hosting events, creating written or video content, and being in charge of various social media channels like Twitter, Reddit, GitHub discussions, Discord or Slack. Where? Wherever the community is more active and in places, having a community will be beneficial for both the company and the members. For example, moving a community from Slack to Discord to have more interpersonal connection with the members through weekly live events with the team members. - Content-focused DevRels: This is the most common type of DevRel in the wild. They focus on developer education, crafting content around the product, written and/or visual. Where? Social media, official accounts, Discord, YouTube, Podcasts, Twitter, and anywhere posting content is relevant to the product's goals. - Product-focused DevRels: They help craft a smooth experience for developers interested in using the product. They usually rely on user feedback on the pain points the process has and try to eradicate them. How? They work on the documentation, guides, tutorials, code samples and templates for the product. Now that you know the most prominent types of DevRels, we can see they often overlap, especially content- and community-focused DevRels. This is because, ultimately, DevRels job is to advocate for the developers that make part of the communities they're managing and creating content for. This is the first article on my What even is a DevRel?!! series, so if you have any topics or specific questions you'd like me to cover make sure to leave them in the comments! I'll love to answer them in upcoming posts. Thank you for reading. I hope you learned something new today! Yuri Santana is a Developer Relations Advocate at Fonoster. Check out more of Yuri's work on a personal blog , and if you have any thoughts feel free to connect on Twitter .

This is a post from DevRelX. DevRelX was a community-driven platform by SlashData dedicated to advancing Developer Relations (DevRel), Developer Marketing, and Developer Experience professionals. It provided research, insights, and resources through initiatives like the Future Developer Summit & the DevRelX Summit, the DevRelX Podcast, and a book. DevRelX created a vibrant space for learning, connection, and discussion within the global DevRel community, until the community was sunset in 2023 as SlashData shifted its focs to wide Technology Research. As you already know, we started this year trying to answer, among others, a burning question - What are the main challenges for developer programs? We just closed our 10th Developer Program Leaders survey, where our goal as always, was to understand your and your peers' challenges, how other DevRel professionals prioritise resources and activities, justify the value of their developer program, and offer insights into how you compare against industry’s practices, especially in the times of uncertainty. Now, we want to offer you and the rest of the community access to data, allowing for data-backed decisions to make your developer program aligned with developers’ priorities and make them want to keep coming back! A big thank you if you supported our recent survey by adding your voice and spreading the word. If you missed the opportunity to chime in - keep an eye out for the next one! As always, DevRelX Community members get the news first. 😉 Developer Program Leaders Forum Now that the survey results are in, it’s time to look into its findings together! On May 11th we are hosting an interactive session where we will discuss Q1, 2023 key findings and their impact on the industry. And we would love for you to be a part of it! Save the date & RSVP here Join if you're in pursuit of answering questions like: What are the main challenges DevRel professionals are facing in 2023? How you can use your available resources to meet these challenges and scale sustainably? How you can turn the knowledge you already have into wisdom that will help you unlock developer-led growth? This session will be supported by our Data Journalist, Richard Muir, who will present the survey results and address your questions live. We'll also have a panel of Developer Program Leaders Forum experts and community members joining us for the discussion. We strongly believe that open discussions, community support and knowledge sharing are key to success and innovation in our industry, individually and collectively. Join us if you feel the same! Transforming words into action, we are taking it a step further and introducing Developer Program Leaders Forum as an extension to our last year’s roundtables. The Forum will consist of DevRelX community members and ambassadors, inspiring, creative and thought-leading Developer Relations professionals. The Forum will come together twice a year, with experts taking turns each time, to discuss the latest Developer Program Leaders survey results and industry trends. Meet our experts Let’s welcome our first Developer Program Leaders Forum crew - Katie, Wesley, Vera, Yuri and Kamran! To get to know them better or source additional inspiration, we invite you to take a look at some of the knowledge nuggets they have already shared with our community. ⭐ Katie Miller Director, Developer Marketing, Slack Impact Via Influence: Keys to DevRel Success within the Organization video + audio - Panel at the DevRelX Summit (2022) Step Up Your DevRel Game - Panel at our Summit (2020) What makes a great developer event? - Chapter in Developer Marketing and Relations: The Essential Guide (2020) Developer Events - Podcast recording (2020) ⭐ Wesley Faulkner Sr. Community Manager, AWS Drafting impact-driven DevRel Strategy - Panel at the DevRelX Summit (2022) Setting up For Success in Your Next Role: Where to Start? - Community Session (2022) ⭐ Yuri Santana Developer Relations Advocate, Fonoster What even is a DevRel? | Part 1 - Article (2023) The importance of documentation in the DevRel space - Article (2022) How to Increase Engagement Within Your Community - Article (2022) ⭐ Vera Tiago Manager, Developer Advocacy, OutSystems Developer Journey: Key Metrics and Initiatives to Drive Success video + audio - Panel at the DevRelX Summit (2022) Between the developers and the business - Podcast recording (2022) ⭐ Kamran Ayub DevTool Onboarding Specialist, Lovely DevEd Kamran is always sharing fantastic insights and tips with our members on a spectrum of topics in Developer Education, and tooling. To name a few: L earning friction , S etting up a Github repository , C ertificates for developer training and more! Are you in? Join the first-ever Developer Program Leaders (DPL) Forum session on May 11 to contribute to the discussion and support our future surveys and if you’d share the spotlight at the next edition! 🙋 Would like to host the next community-led session? Connect with our team! To enable learning and experience sharing among our community members, we bring you DevRelX Community Sessions, hour-long online roundtable discussions. Each session is facilitated by a prominent community member and prompts peers to discuss challenges and share insights on topics that matter to the community the most!

This is a post from DevRelX. DevRelX was a community-driven platform by SlashData dedicated to advancing Developer Relations (DevRel), Developer Marketing, and Developer Experience professionals. It provided research, insights, and resources through initiatives like the Future Developer Summit & the DevRelX Summit, the DevRelX Podcast, and a book. DevRelX created a vibrant space for learning, connection, and discussion within the global DevRel community, until the community was sunset in 2023 as SlashData shifted its focs to wide Technology Research. The distributed transaction ledgers and smart contracts that comprise blockchain technologies have applications in a wide range of industries, particularly in finance, logistics, and government. Today, we present an overview of who is involved in blockchain development and which blockchain platforms they use. Earlier on, we discussed the state of blockchain development in detail in our webinar and you can find a link to watch it below. Engagement with blockchain technologies Of the three blockchain technologies we track in our survey, non-fungible tokens (NFTs) garner the least attention from developers – 58% of them show no interest, likely due to their perception as a novelty technology. On the other hand, cryptocurrencies are most salient to developers – 27% are either learning about or currently working on such projects, and non-cryptocurrency blockchain technologies are very close behind, with 25% of developers similarly involved. We discussed this topic in detail in our webinar on the state of Blockchain Development. We will focus solely on blockchain applications other than cryptocurrencies, as these technologies have the widest range of use cases and thus the most potential to shape our world. We’ll begin by looking at developers’ engagement with blockchain technologies from a regional standpoint and then through the lens of experience in software development. Finally, we’ll give an overview of which blockchain platforms are being used. A regional view of Engagement with blockchain applications Engagement with blockchain applications other than cryptocurrencies, referred to as blockchain applications from here on, varies greatly depending on where developers are located. North America and East Asia excluding Greater China are hotbeds of blockchain development – 15% and 12% of developers in these regions, respectively, are currently working on blockchain applications, with another 17% learning about the technology in both regions. North America and East Asia are hotbeds of blockchain development Further down the list, we see that while the Middle East & Africa has a smaller proportion of developers actively working on blockchain projects; it has the highest incidence of those learning about them (20%). This suggests that the Middle East & Africa could well become important for blockchain development in the future. Indeed, given the region’s history of rapid adoption of new foundational technologies – exemplified by Africa’s mobile banking revolution – blockchain applications in finance and banking are particularly exciting here – though the data suggests that there may still be some way to go. Finance and banking professionals in the Middle East and Africa are more interested in blockchain technologies than finance and banking professionals in other regions. About a quarter of professional developers in the Middle East & Africa who are interested in blockchain technologies are also working in the finance and banking sector. It seems these developers have seen the potential for this technology to shape and disrupt the sector and are getting a head start. Looking at this from the other side, we see that the proportion of finance and banking professionals who are currently working on or learning about blockchain applications is broadly in line with the average for the region (31% vs 33%). However, the proportion who are interested in blockchain applications is 29% higher (37% vs 29%). This is the highest incidence of interest in blockchain applications amongst finance and banking professionals across any region and indicates that blockchain applications could play a pivotal role in this industry in the future. How does experience affect engagement with blockchain applications? Developers with 6-10 years of experience are the most likely to work on blockchain projects. It’s likely that these developers have reached the point in their careers where their technical skills are sufficiently advanced to enable them to work on such demanding projects. On the other hand, we see that the least and most experienced developers are the most likely to be disinterested in such projects. Those with less than a year under their belts have yet to build their knowledge, while the most experienced developers may be looking to maintain some stability in their careers and are reluctant to change tack. Many of the least experienced developers are actively learning about blockchain technologies. They constitute a strong pipeline of future contributors. Developers with 11-15 years under their belts show the most passive interest in blockchain applications – whilst they aren’t learning about or working on such projects, 32% are interested in some way. These developers are at the zenith of their careers and whilst they are some of the least likely to be learning about the technology, they are also some of the most likely to be currently working on it. These developers are likely keeping a close eye on developments in the space – should they spot an opportunity, they will be able to pivot their considerable experience to become effective contributors to the space. Interestingly, although we see that the least experienced developers are less likely than their counterparts with 1-15 years of experience to be currently working on blockchain applications, they are only slightly less likely to be learning about these projects. This demonstrates that although they lack the skills to be active contributors, the myriad applications and potential of blockchain applications are a powerful draw. We can expect that, as learning materials improve and the barriers to entry reduce – as is the case with many technologies – over the next few years, developers will be able to get involved in blockchain projects much earlier in their careers. Which blockchain platforms are most popular? Looking at the specific blockchain platforms that developers report using, we see that Ethereum is clearly dominant amongst learners and those actively developing alike. It’s also unique amongst the blockchain technologies that we ask about, in that it is the only one which is more popular amongst those learning about the technology than those who are currently working on it. This indicates that Ethereum’s ecosystem is in good shape – not only is it large, but it also has a healthy pipeline of new contributors. Although new contributors are certainly good news – the utility of a blockchain rises with the number of applications that use it – a large influx can also create problems. For example, too many transactions on a network can slow things down severely and greatly increase the price of a transaction. For example, when CryptoKitties surged in popularity, the cost of a transaction on the Ethereum network increased ninefold, from ~$50 to over $450 . Such is the price of success. This said, Ethereum’s recent transition to a proof-of-stake model is expected to reduce energy consumption by 99.95% and makes the platform more scalable, secure, and sustainable, potentially mitigating this pitfall. The Binance blockchain platform benefits from its association with the Binance crypto exchange and its interoperability with the Ethereum blockchain. Further down the list, Binance Smart Chain is the second most widely used blockchain platform and is used significantly more by active developers than learners. Here, the Binance Smart Chain not only benefits from its association with the Binance cryptocurrency trading platform, but also its interoperability with the Ethereum blockchain. We also see a similar story with the IBM Blockchain platform – this platform is based on open-source blockchain technology managed by the Linux foundation and clearly benefits from the backing of these two large organisations and their developer and business communities. Despite the hype, blockchain technologies are still somewhat in their infancy. Blockchain, much like cloud computing fifteen or so years ago, has the potential to underpin and enable many other technologies and experiences, but as we saw earlier, only 9% of developers are currently working on such projects. Rather than affecting an instant technological transformation, blockchain technologies have the opportunity to become a foundational technology on which our digital experience sits, much like TCP-IP – the building blocks of the internet – and developers will be key players in shaping this particular view of the future. Thank you for reading! Hope you found it informative!

This is a post from DevRelX. DevRelX was a community-driven platform by SlashData dedicated to advancing Developer Relations (DevRel), Developer Marketing, and Developer Experience professionals. It provided research, insights, and resources through initiatives like the Future Developer Summit & the DevRelX Summit, the DevRelX Podcast, and a book. DevRelX created a vibrant space for learning, connection, and discussion within the global DevRel community, until the community was sunset in 2023 as SlashData shifted its focs to wide Technology Research. 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 SlashData 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. It was done 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, the 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. SlashData 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 .

This is a post from DevRelX. DevRelX was a community-driven platform by SlashData dedicated to advancing Developer Relations (DevRel), Developer Marketing, and Developer Experience professionals. It provided research, insights, and resources through initiatives like the Future Developer Summit & the DevRelX Summit, the DevRelX Podcast, and a book. DevRelX created a vibrant space for learning, connection, and discussion within the global DevRel community, until the community was sunset in 2023 as SlashData shifted its focs to wide Technology Research. Listening to developers' feedback in recent years, it became clear that our community members face anxiety, and burnout and are trying to find ways to improve their overall health and well-being. If you have been around the tech industry and developer communities for a while now, you might have observed an increased need to address these topics in your communities too. We wanted to learn more about our developers’ experiences and what is a better way than asking? In Q1 we ran a survey focusing on developer well-being and we are ready to share the results with everyone in the space! State of Developer Wellness Report With this week being Mental Health Awareness Week in the UK (15th – 21st May) it seems fitting to announce the launch of our State of Developer Wellness report. The report provides insights from our Developer Nation community including workplace experiences, burnout, mental wellbeing, happiness and lifestyles. We hope that the report will raise awareness around the importance of work well-being for developers and creators, and encourage more discussions within developer communities. Our first State of Developer Wellness Survey reached 870 respondents from 91 countries around the world. The report covers: Distribution of Developers based on their Workplace Setup Remote work, how it affects their mental well-being, do developers feel their employers care about their wellbeing Developer burnout How often developers have felt burnout in the last three months, how do they decompress and relieve stress, are they successfully managing their workplace stress? Developer Happiness and Health Lifestyles We encourage everyone to read the report and share it with their colleagues and peers. If you’d like to invite share it with developers in your community, here is the original announcement from Developer Nation . How developer community builders are addressing developer wellness? While working on the survey, we also reached out to the members of our DevRelX community , comprising of Developer Advocates, DevRel practitioners and community builders, asking if they’re addressing burnout and overall wellness in their respective developer communities, and here are the results. The overwhelming majority (62%) of the respondents are not addressing wellness within their communities. On the positive flank, 38% to some extent include wellness-related topics in their community activities, of which 60% are actively promoting wellness within their developer programs. Wellness tips from our team A big thank you to all developers and developer community builders who supported our first survey and the team, without whom this report would not have been possible. Here are wellness tips from some of our team members. Get your thoughts, ideas and worries out onto paper, break your tasks into manageable chunks, learn breath work, get out in nature, stay hydrated, keep moving during the day, listen to a fun podcast, and start every day with the question "how can I be of service to others today?" - Vanessa Measom, Developer Success Executive Organise your thoughts, your day, and your tasks. Stay active and don’t hesitate to reach out for help. Anastasia Alexopoulou, Senior Partnerships Manager For folks working remotely: invest in a good work desk and chair and separate it from your leisure space. Having a good essential aromatic oil in a diffuser also helps lighten the mood sometimes 😉. Don’t hesitate to change your work scenery; cafes, mountains and co-working spaces can be great places to work from. Ayan Pahwa, Developer Advocate It's ok to feel overwhelmed. It's not ok doing nothing about it. Find your passion and let it fill up your batteries. Fight energy draining with energy-boosting activities. Motorcycle rides do that for me. Stathis Georgakopoulos, Product Marketing Manager If you work remotely, adopt a pet. They will be your companion, distraction and a reminder of a different, stress-less way of being. If you're an anxious type, consider alternating your coffee with decaf - it also helps your nutrient absorption! Viktorija Ignatavičiūtė, Sr. Community Lead Find your optimal work hours. Discover the time of day when you’re most productive and build your schedule around it. Also, remember to take regular breaks. Coffee or Tea breaks work ☕️. Gottfried Moh, Community Lead Let’s build on a culture of wellness that promotes the mental, physical and emotional well-being of the developer industry! Organisations that can help with burnout: Johns Hopkins University BurnoutAid Rehab4Addiction

This is a post from DevRelX. DevRelX was a community-driven platform by SlashData dedicated to advancing Developer Relations (DevRel), Developer Marketing, and Developer Experience professionals. It provided research, insights, and resources through initiatives like the Future Developer Summit & the DevRelX Summit, the DevRelX Podcast, and a book. DevRelX created a vibrant space for learning, connection, and discussion within the global DevRel community, until the community was sunset in 2023 as SlashData shifted its focs to wide Technology Research. 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 SlashData's 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 the 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. Experimenting with AI in Developer Relations We also wanted to take a closer look into how Developer Relations are adopting AI in their work. We asked our DevRelX Community members to share their take on how AI technologies are affecting DevRel and developer communities. Ash Ryan Arnwine , Director of Developer Relations, Nylas, shared inspirational ideas for experimenting with these new technologies. Ash also wrote a blog post about how DevRel teams can start using AI. Ash: At Nylas, our DevRel team is using a framework of four questions to help us explore where AI can be useful in key areas of our work. My hope is that our team can grapple with emerging AI capabilities while keeping a couple of guiding principles in mind. First, the current wave of generative AI is the newest "bicycle for the mind"; it doesn't need to solve every problem perfectly to be a valuable tool. It's on us to learn this tool and wield it constructively in the service of our developers. The second principle is related: we experiment aggressively in private; we ship to developers with care and consideration. As an example of our framework in practice, we've used ChatGPT and GitHub Copilot to aid in writing a code sample showing developers how to build an AI-enhanced email spam filter. In other words, we're using AI to aid in completing the meta task of inspiring developers on ways to enhance their Nylas integrations with AI. On the developer experience side, it feels like the possibilities are almost infinite—as a simple example, I gave a talk at apidays New York a couple of weeks ago that highlighted the potential of enabling developers to "talk" to your OpenAPI spec. It's all so much fun. And the more we play, the better informed our product ideas and AI-enhanced DevRel work can become." Have ideas to share? Join the conversation with Ash and more peers on DevRelX Slack . 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

This is a post from DevRelX. DevRelX was a community-driven platform by SlashData dedicated to advancing Developer Relations (DevRel), Developer Marketing, and Developer Experience professionals. It provided research, insights, and resources through initiatives like the Future Developer Summit & the DevRelX Summit, the DevRelX Podcast, and a book. DevRelX created a vibrant space for learning, connection, and discussion within the global DevRel community, until the community was sunset in 2023 as SlashData shifted its focs to wide Technology Research. At DevRelX , we take great pride in supporting organisations and communities that contribute to the diverse and inclusive evolution of the tech industry. This time we want to bring into the spotlight the Ada Developers Academy whose mission is to prepare women and gender-expansive adults to be software developers while advocating for inclusive and equitable work environments. Ada primarily serves and addresses the needs of Black, Latine, Indigenous Americans, Native Hawaiian & Pacific Islanders, LGBTQIA+, and low-income people. Gender diversity brings substantial benefits to individual companies and the tech economy at large. We can see more companies recognising the importance of diverse workspaces. According to SlashData’s research , as of Q1 2023, nearly a quarter of all developers (22%) self-identify as female, up from 19% two years ago . Still, many companies struggle to recruit and retain diverse talent – that’s where Ada Developers Academy comes in. Ada Academy is a one-year, tuition-free coding school that fast-tracks women and gender-expansive folks into junior software developer roles. Through six months in the classroom and five months in an industry internship with one of our company partners, Ada students build the skills and experience they need to become developers. We develop engineers who are highly skilled and collaborative; graduates are experienced in practical, team-based software development and learning new technology rapidly. The results of their work speak for themselves – 94% of Ada graduates are hired into full-time software engineering jobs within six months of graduation. Meet Katherine Abrikian Katherine is an Ada alum and fills her spiritual cup through volunteerism and community ties. She builds up new coders as a mentor to incoming Adies and creates lasting relationships from city to city. Strong community ties and giving back can fuel your spirit – because when you’re around your people, something just clicks. Community is different for everyone. It can inspire, empower, or be a springboard for innovation. Helping not only feels good, but it can also make a difference. Build connections with your local organizations and get involved today. You never know the power of your contribution. Deepening Connections in Community Roots Share with us how you are currently involved with your community and what that means to you. Community involvement has always been important to me. Everywhere I go, I seek out opportunities to deepen community connections, give back through volunteerism, and show up for others. My family and I have moved three times in the past three and a half years, so my community involvement has been, at times, virtual, allowing me to maintain connections, and at times in person, in forging new connections. We moved into our current neighbourhood about a week before the school year started this past August. In applying to Ada, I was particularly drawn to Ada’s model of collaborative support. I’m continuing to deepen my ties with my new communities. I’ve volunteered at my son’s school, and I’m grateful to be active in supporting fellow Adies outside of the mandatory classroom requirements (facilitating review sessions, helping to think through blockers, providing a listening ear) and receiving their trust and support in turn. Making time for cultivating community and giving back outside of the 9-5 work schedule can be exhausting! What inspired you to get involved? What keeps you coming back or pushing forward? There’s a certain spiritual nourishment that comes from being part of an active community where you give, but also, when you begin to feel depleted, you can receive something in return. That something received can vary a lot. It might be the vicarious joy of a community member’s personal or professional victory. It might be some sort of direct support. One recent reaffirming moment for me occurred during our first week in our new neighbourhood. My family and I stopped in at Everyday Sundae and were immediately granted the gift of community. The owner welcomed us, saw our toddler, and took the time to invite us to a community event for children that was coming up soon. Whenever we stop in there now, we chat and deepen that connection. For me, it’s these sorts of connections that help to make a place feel like home. I’m determined to do my part in that work, pay the kindness given to me forward, and multiply that kindness in the world. Why does community building bring you joy? About two months after starting with Ada, I heard about Black Code Collective from a member of the Ada community and joined. It’s been such a blessing to have this community of Black tech workers, where we can talk about the issues that concern us, from the purely professional to the cultural. I went to a meet-up in December, and we took up a full third of the bar we were meeting in. Seeing so many Black people with connections to tech in one space was so powerful. Being an active part of that community absolutely brings me joy. What organizations would you like to share with folks to learn more about? Black Code Collective – supporting Black joy and Black progress in tech Everyday Sundae – amazing ice cream, feels like coming home Any other thoughts you’d like to share about being a volunteer, finding your community, or anything else? Community connection got more difficult during the pandemic in some ways, but it’s still possible. I message and call mentees when we can’t meet face-to-face; I’ve facilitated group sessions virtually. Connecting with people who don’t have a lot of resources gets even tougher, but if everyone is committed and sees a benefit, it can work. In terms of finding a community, if you’re already established in the community, and you see someone new, please reach out to welcome them and see what commonalities exist. Everyone has to start somewhere, and feeling welcomed is a huge leg up. You can connect with Katherine on LinkedIn . Since our founding in 2013, Ada has served over 1,000 participants and generated $50M in new salaries for women and gender-expansive folks in the tech economy, narrowing gender and racial equity gaps in one of our most prosperous and influential sectors. Learn more at www.adadevelopersacademy.org .

This is a post from DevRelX. DevRelX was a community-driven platform by SlashData dedicated to advancing Developer Relations (DevRel), Developer Marketing, and Developer Experience professionals. It provided research, insights, and resources through initiatives like the Future Developer Summit & the DevRelX Summit, the DevRelX Podcast, and a book. DevRelX created a vibrant space for learning, connection, and discussion within the global DevRel community, until the community was sunset in 2023 as SlashData shifted its focs to wide Technology Research. In our previous encounter, we discussed what is a DevRel, their types and what they actually do. Now, let’s dive deeper into DevRel and talk about how to create good and engaging content. We see content all around us, but what is the importance? How can you start creating content? Where? How to improve your content? Content is such a broad term, it basically means getting an idea and creating visual or written content to present it to the world. The better the content you generate, the more likely users will come back and engage with your community and with each other. On the business side of things, it will help you increase engagement, and clients are more likely to continue investing in your product. The most common type of content we see out there is technical writing. It's more common than we think! We see it with manuals, instructions on how to take medicine and more. But what exactly is technical writing? Technical writing Technical writing is designed to make difficult concepts as easy as possible for readers. Every time you read a user guide, tutorial, manual, case study, etc, those are common examples of technical writing in action. Technical writing is a core element within any community, especially when you're advocating for a product. Documentation is the first direct contact you have with developers and users interested in learning about and using a certain product. It is designed to explain specialized information to those who are not familiar with it and to help those who are looking to deepen their knowledge. This raises a question: Does technical writing always involve diving deep into technical content or do we need to separate our audiences? Sometimes we just want to share content with our community without technical intent. Is that possible? Developers vs Users When creating content, which audience should you focus on? Depending on the type of audience that you wish to target, you will have to take a different creative style to meet the particular needs of each group. We can identify two main audiences: developers and users. Developers Developers play an active role when consuming content or reading documentation. Having clear guidelines will make them want to contribute and help with the product, ultimately helping improve the code, documentation, and community. They usually focus more on: API (application programming interface) documentation: which usually defines how applications communicate with each other using requests and responses. Read Me’s: Work as a general description of the product usually with the source code. System Documentation: Help describe the product, technical design, software requirements and more. Release notes: Where they learn about the product launch, features or errors they’ve worked on or information on the latest version of the product. But it is not unusual for developers to be users and vice versa. Users They can play an active or passive role when consuming content. They want to use and understand the product to the best of their abilities. Some ways to target users are to write easy-to-follow guides, and tutorials and guide them to external sources when you need to expand on certain topics. Users tend to focus more on: How to guide: Help the user reach a goal. The whole purpose is to help the user complete a task. Tutorials: Leave the user with knowledge of a concept or process they didn’t have before. Explanations: Work as a way to shine light on more specific topics they might not know about. Reference documentation: They are made to share with the user more technical descriptions and concepts about the product. It is important to keep in mind that it is possible to keep both audiences balanced whenever you're creating content. But keep in mind, in some cases both audiences need to be addressed in different ways throughout the content creation process. User-focused documents should have less technical terminology than when we are talking to developers, always taking into account their background, experience and the different types of content that the two audiences focus on. How to start creating content Here's the layout of the content creation process you'll be following most of the time. Keep in mind you don't need to strictly follow one step after the other. There’ll come a time when you start with the investigation, get the idea, generate the content and then identify your audience, check for mistakes and ultimately post it. The general steps are: Ideate on a topic - what challenges do you want to help your audience with? Make sure that is stated from the get-go as it will help you shape your next steps around it. Investigate - do your research on the subject. Include your personal expertise, but make sure you cross-check other resources on similar subjects. Or perhaps understand what unique angle you can bring to this subject? Create an outline - it will help your storytelling. If you’re not following the structure, it’s most likely your readers/viewers won’t be able to follow it along with you. Identify your audience - remember the challenge you identified? Make sure this is tailored to a specific audience you’re catering to. Use this as a guide to shape not only the content itself but also the best style and format to deliver it. Create the content - start creating your draft, and find teammates or peers to bounce ideas off and/or share your draft for a peer review. Another pair of eyes can be extremely helpful for any content creation efforts! Check for errors - even if you’re the only DevRel in your organization, you can use different tools for fact-checking or grammar errors to make your content spotless. Some of the tools I use are Grammarly or you can also use some other free online grammar checkers. Publish - once you’re ready to go live, publish your work and make sure to also let others know about it. Reach out to your network on social media and the online communities you’re part of. People are likely to cheer for you and also can provide feedback that will help you improve. Repeat! That’s a no-brainer but is often left off the list. In the meantime, you will gather a network, community, and audience around you, who will be excited to see your new content out, so don’t forget to keep them engaged. A more tactical approach and regularity will also help you acquire new audiences along the way. You should and are encouraged to find what process or steps work for you and make you a productive content creator. Where to start creating content It’s quite easy to get trapped in the latest social media apps, but before you start posting content, for a company or your personal brand, you need to know where your users are the most active or where you want to start building a community. Where are your users more active: You want your content to be consumed by your target audience. Start by identifying which social media platforms they are more active on, which communities they frequent and what type of content is their preferred whether that is visual, written or audio. Where do you want to start a community: We often see communities being moved from one platform to another. One way to prevent this major decision is to take a step back and identify where your target audience has the least amount of resistance when joining your community, and which platform will make it easier for them to reach out to the team or share their feedback accurately. Remember that you want to effectively remove any pain points that will make users not join your community or consume your content, so by placing yourself in your users’ perspective, you help prevent some major pain points that are preventing your community from growing in both members and engagement. Common mistakes Now that we have a clear idea of the basic steps towards creating content, let's dig deeper into some of the most common mistakes you can avoid that will help you be an effective content creator. Assuming that the person consuming the content has the same technical knowledge as the one creating it: This limits the number of users and developers that will interact with your content. That's why it's important to know your audience. You should always generate your content based on the different levels of prior education your readers will have, not the ones you possess. Not explaining acronyms: You should always break down the meaning of the acronyms you use in text before actively using them in your content, in parentheses. This is very related to the previous point. Do not assume that the person consuming your content has the same technical knowledge as you. The use of the passive voice: By utilizing the passive voice when creating content, you are at risk of generating less clarity and ambiguity in your sentences. However, this can be addressed by using an active voice, which urges the reader to take action and understand the content they are consuming more confidently. Skipping minor steps you think are given: By skipping minor steps that the content creator believes to be a given, the person consuming the content will be lost and won't know what to do. This is particularly detrimental when the goal is for the user to complete a task or understand a concept. Upgrade your content skills We've gone over some of the most common mistakes to avoid when creating content. Now what makes the content good? What are some things we should be actively adding to our content? Write in simple terms: Depending on your content strategy and keeping in mind your target audience, technical terms can sometimes bring you closer to your users but, most of the time, there is no need to use extremely technical terms when creating content, especially for the public. Think of a way to present your content that is easy for readers to understand, whether or not they have previous experience with the product. Having a style guide: It can help you create a consistent voice and image within the community, the person consuming the content will respond better to the same form and styling of content, terminology and images. It is not necessary to create one, there are many guides on the internet. Being open and encouraging community feedback: This will help you know which content to improve, which guides work, and which ones are confusing. Remember that ultimately you're creating content for the community, so it is best to know from the source what is working for them and what is not. Tracking changes: Having version control will help you track content changes, especially when working with documentation. In case a new feature is removed due to user feedback, you can go back to the old documentation. Inclusiveness and accessibility:** The internet should be welcoming to everyone. Try to avoid idioms to help the international audience understand your content better, think about people who use screen readers, make sure you have good contrast in the design, and if you are going to use screenshots, make sure they are accompanied by alt-text. Ultimately, you should think about the users who find your content online. Is it accessible? Is it easy to follow? Can they easily find what they are looking for? Adaptability and Consistency: You need to be able to adapt and grow within the community, do check-ins and see how you can improve. It's a must for a content creator, and this is not possible without being consistent in your craft. And remember, It may take time, but there's nothing that gets worse due to practising . A good and sustainable content strategy takes a lot of trial and error behind the scenes . It's about figuring out what works for you and your goals but also what resonates with the community. Do not be afraid to reiterate some content you've published in the past with new ideas or in a completely new media format, it's all about practice. So practice on, my friend.