For the fifth consecutive year, we surveyed developers worldwide to understand what makes them productive, what frustrates them, and what they need from their tools and organizations. This year, 15,247 developers from 89 countries shared their experiences.

The findings reveal both continuity and change. Some pain points persist year after year. Others have shifted dramatically—particularly around AI tools, remote work, and developer burnout.

Key Findings

• 73% of developers now use AI coding assistants regularly (+45% from 2024)
• Developer satisfaction with tooling reached an all-time high of 7.2/10
• Build times remain the #1 friction point for the third year running
• Remote-first developers report 18% higher satisfaction than office-first
• Burnout rates decreased slightly to 42% (from 48% in 2024)

The AI Revolution in Development

The most dramatic shift we've observed is the adoption of AI coding assistants. In 2023, only 28% of developers used AI tools regularly. By 2025, that number has reached 73%. More striking: developers using AI report completing tasks 40% faster on average.

But the impact isn't uniform. AI tools excel at boilerplate code, documentation, and well-defined problems. They struggle with complex architecture decisions, novel algorithms, and code that requires deep domain knowledge.

AI hasn't replaced developers—it's amplified them. The gap between senior and junior developers has actually widened, because seniors know how to leverage AI effectively.

The Productivity Paradox

Despite better tools and faster computers, developers report only marginal improvements in their perceived productivity year over year. We call this the 'productivity paradox'—and our research suggests several causes.

Complexity Creep

As tools get better, systems get more complex. The JavaScript ecosystem alone has grown by 340% in five years. Developers spend more time managing complexity than they save through better tooling.

Context Switching

The average developer uses 11 different tools daily (up from 7 in 2020). Each tool switch costs cognitive overhead. Integrated development environments that reduce tool switching show the highest satisfaction scores.

What Developers Want

We asked developers to rank what would most improve their work experience. The results were clear and consistent across regions, company sizes, and experience levels:

• Faster build and test cycles (requested by 67%)
• Better documentation (59%)
• Fewer meetings (54%)
• More autonomy in technical decisions (51%)
• Clearer product requirements (48%)

Notably, compensation ranked only 6th. Developers prioritize their work experience over pay increases—a finding that has held consistent for three years.

Recommendations

Based on our findings, we recommend organizations focus on these high-impact areas to improve developer experience:

• Invest in build infrastructure: Every minute saved in build time multiplies across every developer, every day
• Consolidate tooling: Reduce the number of tools developers need to context-switch between
• Protect deep work time: Implement meeting-free blocks and async-first communication
• Document decisions, not just code: The 'why' is more valuable than the 'what'
• Measure developer experience: What gets measured gets managed

Looking Ahead

The developer experience landscape continues to evolve rapidly. AI tools are just beginning to show their potential. New paradigms like local-first development and edge computing are reshaping how we think about architecture. And the ongoing experiment in remote work continues to yield insights about collaboration and productivity.

We'll continue tracking these trends in next year's report. Until then, the data is clear: investing in developer experience isn't just good for developers—it's good for business.