What kind of content does the SlashData Blog cover?

Our blog shares analyst foresight based on data-driven insights on developer trends, AI engagement, adoption and AI tool benchmarks, cloud, DevOps, open source, tooling, and emerging technologies. We publish: Research highlights from our global developer surveys Analysis of developer adoption and sentiment trends Commentary on AI, productivity, and tooling shifts Strategic perspectives for product, marketing, DevRel, and engineering leaders Every post connects market signals to real business cases and decisions.

Who writes the posts on the SlashData Blog?

Our posts are mainly written by Alvaro, Bleona, Liam, Nikita, Jed our SlashData analysts, the de facto subject-matter experts. Our analysts behind the articles: Design and run our independent, global developer research programmes Analyse behavioural and sentiment data Work directly with technology leaders across product, marketing, and engineering You’re reading insights from the same team trusted to inform high-stakes strategic decisions. Some posts are written by Andrea, Stathis, Petro, and Natasa, who help match the data to the business cases and problems we are solving.

How is the blog different from your formal research reports?

Our reports deliver deep datasets and structured analysis. The blog makes those insights timely and accessible, and does not go as deep. Our blog articles Explain what the data means in practical terms Connects trends to current industry shifts Surfaces emerging signals earlier Highlights implications for roadmap, positioning, and growth Think of it as applied research in motion.

Who is the SlashData Blog for?

The blog is for leaders and decision-makers who need evidence, not noise. Including: Heads of Product Product Marketing leaders DevRel and Developer Marketing teams CTOs and VP Engineering AI strategy and tooling leaders If developer behaviour impacts your revenue, roadmap, or positioning, this content is for you.

Are the insights based on real data or opinion?

Our insights are grounded in large-scale, global developer research. We: Run independent developer surveys across regions and technologies Apply rigorous data cleaning and weighting Analyse longitudinal trends When we share a viewpoint, it is anchored in observed data, not speculation.

Can I use insights from the blog in business cases or presentations?

Absolutely. Just make sure you credit us as this adds more weight to your presentation. If you are unsure about whether you can use a piece of content, please contact us. Many readers use our blog to: Support internal discussions Frame executive conversations Validate strategic assumptions Identify emerging risks or opportunities For deeper validation, we also provide tailored data and advisory support.

How often do you publish new blog content?

We publish regularly as new trends emerge and new research waves are analysed. Our surveys run every 6 months, so as soon as the data is in, our analysts dive into it. Through our tailored surveys and collaborations with large organisations in Tech, we explore more focused topics and write about them. Topics evolve with the developer ecosystem, especially across AI, cloud, developer productivity, developer awarenes and adoption and market shifts.

How can I stay updated on new insights?

You can subscribe to our newsletter or follow SlashData on our social media pages. The newsletter is delivered to your inbox every 2 weeks and features an analyst deep dive.

The Rise of the Builder - and Other Developer Trends We're Measuring in Q3 2026

Liam Bollmann-Dodd
11 minutes ago
3 min read

The 32nd Developer Nation survey is now in the field, gathering insights from more than 15,000 software developers worldwide. Here are some of the key trends and insights you can expect from SlashData in Q3 2026, including builders, developer productivity, cloud adoption, and the future of software development.

Meet the builders: shipping software without a developer background

The biggest change on our 32nd wave is the onboarding of “builders” into our survey, a new group we’re tracking for the first time. Builders are people without traditional developer experience or backgrounds who are using AI tooling to build applications or services. As we discussed in our whitepaper, we’re looking at those building for personal use, those augmenting their internal workflows, and those building consumer-facing applications. Builders represent an emerging segment of the wider developer ecosystem rather than a replacement for traditional software developers. SlashData will be able to provide a picture of who these people are, how they engage with AI tools and the ecosystem, how AI has changed their working lives, and where they overlap with the traditional developer audience.

How AI is reshaping the day-to-day

Beyond builders, this research wave also digs into how AI is changing the way existing developers work. Spec-driven development, where developers define detailed requirements, constraints, and expected outcomes before AI-assisted code generation, is one of the new “buzzwords” being pushed to describe this shift. Our research will provide a clearer read on how prevalent the approach actually is, and for those doing it, what goes into their specs and how they feel about the approach philosophically.

There’s also a lot of talk about the developer role shifting from writing code to reviewing it. It’s unlikely many developers dreamed of reviewing code all day, so SlashData is aiming to understand how prevalent AI code review really is, and who’s sending developers this AI-generated code (other developers, management, non-developer staff), and whether they integrate it, correct it, or scrap it outright.

The future of developer teams: skills, seniority, and the junior developer squeeze

With so much focus on how AI is reshaping developer life, we’re asking developers directly where they think the future of development teams is going: what skills they expect to matter, how they feel the current implementation is going, and the impact on junior and emerging developers. Combined with expanded developer wellbeing metrics, the aim isn’t just to say where developers think the future is heading, but how they’re feeling as they cruise towards it.

Why DORA metrics stop short of developer productivity

Where the future-of-teams work captures what developers predict and feel, SlashData is also going deeper on how effectiveness itself gets measured. This wave continues our move into metrics that extend beyond traditional DORA software delivery metrics, looking at what actually drives developer productivity, happiness, and effectiveness within organisations — split across organisational practices and benefits, and the value and meaning developers draw from their work. The goal is a wider, more holistic understanding of what it means to be an effective, happy developer, not just a faster one.

Tracking the technology developers rely on: cloud provider preference and on-device AI

SlashData continues to track the technologies developers use and integrate release over release, and this wave adds two areas we see as important drivers of where things are headed. Small, on-device models have fallen out of the spotlight as large open-weight models capture media attention (such as DeepSeek and Moonshot AI’s Kimi K3), but for many analysts, on-device AI is where the future of LLMs actually lies, so we’re assessing its scale in 2026 and asking developers where they see the best use cases emerging.

Alongside this, we’re interrogating cloud provider preference across application types (including AI agents and generative AI services, alongside web/mobile applications, data analytics, CDNs, and serverless), aiming to sidestep vendor benchmarks and spec-sheet marketing in favour of what developers actually choose when given a free hand.

Want early access?

Reach out to the SlashData team, a leading research firm focused on the developer economy, to flag which of these you’d like to hear about first, or to make sure you’re kept in the loop when the data lands.