www.docker.com
What's helping devs thrive...
- **Non-local dev environments are now the norm — not the exception**. In a major shift from last year, **64%** of developers say they use **non-local environments** **as their primary development setup**, with local environments now accounting for only **36%** of dev workflows. - **Data quality is the bottleneck** when it comes to building AI/ML-powered apps — and it affects everything downstream. **26% of AI builders** say they’re not confident in how to prep the right datasets — or don’t trust the data they have. … ## 1. ... Great culture, better tools — but developers often still hit sticking points. From pull requests held up in review to tasks without clear estimates, the inner loop remains cluttered with surprisingly persistent friction points. … And among container users, needs are evolving. They want better tools for **time estimation (31% ** compared to 23% of all respondents**), task planning (18% for both container users and all respondents), and monitoring/logging (16%) ** vs designing from scratch (18%) in the number 3 spot for all respondents — stubborn pain points across the software lifecycle. ### An equal-opportunity headache: estimating time No matter the role, **estimating how long a task will take is the most consistent pain point** across the board. Whether you’re a front-end developer (**28%**), data scientist (**31%**), or a software decision-maker (**49%**), precision in time planning remains elusive. Other top roadblocks? **Task planning (26%)** and **pull-request review (25%)** are slowing teams down. Interestingly, where people say they need better tools doesn’t always match where they’re getting stuck. Case in point, **testing solutions and Continuous Delivery (CD)** come up often when devs talk about tooling gaps — even though they’re not always flagged as blockers. ### Productivity by role: different hats, same struggles When you break it down by role, some unique themes emerge: - **Experienced developers** struggle most with time estimation (**42%**). - **Engineering managers** face a three-way tie: **planning, time estimation, and designing from scratch (28% each)**. - **Data scientists** are especially challenged by **CD (21%)** — a task not traditionally in their wheelhouse. - **Front-end devs**, surprisingly, list **writing code (28%)** as a challenge, closely followed by **CI (26%)**. … ### The hidden bottleneck: data prep When it comes to building AI/ML-powered apps, **data is the choke point**. A full **26% of AI builders** say they’re not confident in how to prep the right datasets — or don’t trust the data they have. This issue lives upstream but affects everything downstream — time to delivery, model performance, user experience. And it’s often overlooked.
Related Pain Points8件
Data quality and preparation for AI/ML applications
726% of AI builders lack confidence in dataset preparation and trustworthiness of their data. This upstream bottleneck cascades into time-to-delivery delays, poor model performance, and suboptimal user experience.
Pull request review bottlenecks
6Pull request review is flagged as a top workflow blocker (25% of developers), slowing team coordination and delaying merges. No structured tooling has effectively reduced this friction point.
Time estimation across development workflows
6Estimating task duration is the most consistent pain point across all developer roles (31% of IT professionals, 42% of experienced developers, 49% of decision-makers). This affects sprint planning and project delivery prediction.
Non-local development environment complexity
664% of developers now use non-local cloud environments as primary setup, but this introduces coordination and debugging challenges that weren't present in local-only workflows, requiring new tooling and practices.
Front-end developers struggling with CI/CD pipelines
6Front-end developers list CI configuration (26%) and code writing (28%) as primary challenges. CI/CD complexity isn't traditionally in their wheelhouse but increasingly required.
Monitoring and logging visibility gaps
5Container users need better monitoring/logging tools (16% request improvement), but existing solutions don't provide adequate observability for non-local distributed environments.
Task planning and work coordination
526% of developers struggle with task planning and resource allocation. Container users specifically need better tools for task planning (18%), yet existing solutions don't adequately address this need.
Gap between tooling needs and actual bottlenecks
4Developers report needing better testing solutions and CI/CD tools, but these aren't always flagged as primary blockers. Unclear signal about where tool investment matters most.